Computational systems and methods for monitoring medication events

ABSTRACT

Computer-based systems and computer-implemented methods are described for monitoring medication events for an individual. Computer-based systems include systems for monitoring medication events relating to an individual, including: circuitry for analyzing data for an identifier of a first medication event for an individual; circuitry for analyzing the data for at least one attribute of an individual; circuitry for analyzing the data for at least one attribute relating to a medication during the first medication event; circuitry for analyzing the data for at least one feature of visual information and at least one feature of non-visual information relating to the individual during the first medication event; circuitry for analyzing the received data for a time associated with the first medication event; circuitry for determining a compliance likelihood for the first medication event based on the analyses of the received data; and circuitry for indicating the determined compliance likelihood.

RELATED APPLICATIONS

-   -   U.S. patent application Ser. No. To Be Assigned [attorney docket        number 1011-002-007-000000], entitled COMPUTATIONAL SYSTEMS AND        METHODS FOR MONITORING MEDICATION EVENTS, naming Mahalaxmi Gita        Bangera, Roderick A. Hyde, Jordin T. Kare, Eric C. Leuthardt,        Elizabeth A. Sweeney, and Lowell L. Wood, Jr. as inventors,        filed 24 Aug. 2012.    -   U.S. patent application Ser. No. To Be Assigned [attorney docket        number 1011-002-008-000000], entitled COMPUTATIONAL SYSTEMS AND        METHODS FOR MONITORING MEDICATION EVENTS, naming Mahalaxmi Gita        Bangera, Roderick A. Hyde, Jordin T. Kare, Eric C. Leuthardt,        Elizabeth A. Sweeney, and Lowell L. Wood, Jr. as inventors,        filed 24 Aug. 2012.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application is related to the following listedapplication(s) (the “Related Applications”). All subject matter of theRelated Applications and of any and all parent, grandparent,great-grandparent, etc. applications of the Related Applications, isincorporated herein by reference to the extent such subject matter isnot inconsistent herewith.

SUMMARY

In some embodiments, a system includes but is not limited to a systemfor monitoring medication events relating to an individual, including:circuitry for analyzing received data for an identifier of a firstmedication event for an individual; circuitry for analyzing the receiveddata for at least one attribute of an individual; circuitry foranalyzing the received data for at least one attribute relating to amedication during the first medication event; circuitry for analyzingthe received data for at least one feature of visual informationrelating to the individual during the first medication event; circuitryfor analyzing the received data for at least one feature of non-visualinformation relating to the individual during the first medicationevent; circuitry for analyzing the received data for a time associatedwith the first medication event; circuitry for determining a compliancelikelihood for the first medication event based on the analyses of thereceived data; and circuitry for indicating the determined compliancelikelihood for the first medication event. In one aspect, a systemincludes computer-readable storage medium including executableinstructions for monitoring medication events relating to an individual,the computer-readable storage medium including: instructions foranalyzing received data for an identifier of a first medication eventfor an individual; instructions for analyzing the received data for atleast one attribute of an individual; instructions for analyzing thereceived data for at least one attribute relating to a medication duringthe first medication event; instructions for analyzing the received datafor at least one feature of visual information relating to theindividual during the first medication event; instructions for analyzingthe received data for at least one feature of non-visual informationrelating to the individual during the first medication event;instructions for analyzing the received data for a time associated withthe first medication event; instructions for determining a compliancelikelihood for the first medication event based on the analyses of thereceived data; and instructions for indicating the determined compliancelikelihood for the first medication event. In addition to the foregoing,other system aspects are described in the claims, drawings, and textforming a part of the present disclosure.

In some embodiments, a computer-readable storage medium includesexecutable instructions for monitoring medication events relating to anindividual, the computer-readable storage medium including: instructionsfor analyzing received data for an identifier of a first medicationevent for an individual; instructions for analyzing the received datafor at least one attribute of an individual; instructions for analyzingthe received data for at least one attribute relating to a medicationduring the first medication event; instructions for analyzing thereceived data for at least one feature of visual information relating tothe individual during the first medication event; instructions foranalyzing the received data for at least one feature of non-visualinformation relating to the individual during the first medicationevent; instructions for analyzing the received data for a timeassociated with the first medication event; instructions for determininga compliance likelihood for the first medication event based on theanalyses of the received data; and instructions for indicating thedetermined compliance likelihood for the first medication event. Inaddition to the foregoing, other computer product aspects are describedin the claims, drawings, and text forming a part of the presentdisclosure.

In some embodiments, a method includes but is not limited to a methodfor monitoring medication events relating to an individual, including:analyzing received data for an identifier of a first medication eventfor an individual, the received data originating from at least onemonitoring device; analyzing the received data for at least oneattribute of an individual; analyzing the received data for at least oneattribute relating to a medication during the first medication event;analyzing the received data for at least one feature of visualinformation relating to the individual during the first medicationevent; analyzing the received data for at least one feature ofnon-visual information relating to the individual during the firstmedication event; analyzing the received data for a time associated withthe first medication event; determining a compliance likelihood for thefirst medication event based on the analyses of the received data; andindicating the determined compliance likelihood for the first medicationevent. In addition to the foregoing, other method aspects are describedin the claims, drawings, and text forming a part of the presentdisclosure.

In one or more various aspects, related systems include but are notlimited to circuitry and/or programming for effecting theherein-referenced method aspects; the circuitry and/or programming canbe virtually any combination of hardware, software, and/or firmwareconfigured to effect the herein-referenced method aspects depending uponthe design choices of the system designer.

The foregoing summary is illustrative only and is not intended to be inany way limiting. In addition to the illustrative aspects, embodiments,and features described above, further aspects, embodiments, and featureswill become apparent by reference to the drawings and the followingdetailed description.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1 is a illustrates aspects of a system for monitoring medicationevents relating to an individual.

FIG. 2 depicts a system for monitoring medication events relating to anindividual.

FIG. 3 illustrates aspects of the system of FIG. 2.

FIG. 4 shows aspects of the system of FIG. 2.

FIG. 5 depicts aspects of the system of FIG. 2.

FIG. 6 illustrates aspects of the system of FIG. 2.

FIG. 7 shows aspects of the system of FIG. 2.

FIG. 8 depicts aspects of the system of FIG. 2.

FIG. 9 illustrates aspects of the system of FIG. 2.

FIG. 10 shows aspects of the system of FIG. 2.

FIG. 11 depicts aspects of the system of FIG. 2.

FIG. 12 illustrates aspects of the system of FIG. 2.

FIG. 13 illustrates aspects of the system of FIG. 2.

FIG. 14 shows aspects of the system of FIG. 2.

FIG. 15 depicts aspects of the system of FIG. 2.

FIG. 16 illustrates aspects of the system of FIG. 2.

FIG. 17 shows aspects of the system of FIG. 2.

FIG. 18 depicts aspects of the system of FIG. 2.

FIG. 19 illustrates aspects of the system of FIG. 2.

FIG. 20 shows aspects of the system of FIG. 2.

FIG. 21 depicts aspects of the system of FIG. 2.

FIG. 22 illustrates aspects of the system of FIG. 2.

FIG. 23 shows aspects of the system of FIG. 2.

FIG. 24 depicts a system including computer-readable storage mediumincluding executable instructions for monitoring medication eventsrelating to an individual.

FIG. 25 illustrates a flowchart of a method for monitoring medicationevents relating to an individual.

FIG. 26 depicts a system for monitoring medication events.

FIG. 27 illustrates aspects of the system of FIG. 26.

FIG. 28 shows aspects of the system of FIG. 26.

FIG. 29 depicts aspects of the system of FIG. 26.

FIG. 30 illustrates aspects of the system of FIG. 26.

FIG. 31 shows aspects of the system of FIG. 26.

FIG. 32 depicts aspects of the system of FIG. 26.

FIG. 33 shows aspects of the system of FIG. 26.

FIG. 34 depicts aspects of the system of FIG. 26.

FIG. 35 illustrates aspects of the system of FIG. 26.

FIG. 36 shows aspects of the system of FIG. 26.

FIG. 37 depicts a system including computer-readable storage mediumincluding executable instructions for monitoring medication eventsrelating to an individual.

FIG. 38 illustrates a flowchart of a method for monitoring medicationevents relating to an individual.

FIG. 39 shows a system for monitoring medication events.

FIG. 40 shows aspects of the system of FIG. 39.

FIG. 41 depicts aspects of the system of FIG. 39.

FIG. 42 illustrates aspects of the system of FIG. 39.

FIG. 43 shows aspects of the system of FIG. 39.

FIG. 44 depicts aspects of the system of FIG. 39.

FIG. 45 illustrates aspects of the system of FIG. 39.

FIG. 46 shows aspects of the system of FIG. 39.

FIG. 47 depicts aspects of the system of FIG. 39.

FIG. 48 illustrates aspects of the system of FIG. 39.

FIG. 49 shows aspects of the system of FIG. 39.

FIG. 50 depicts a system including computer-readable storage mediumincluding executable instructions for monitoring medication events.

FIG. 51 illustrates a flowchart of a method for monitoring medicationevents.

FIG. 52 shows a system for monitoring medication events.

FIG. 53 shows aspects of the system of FIG. 52.

FIG. 54 depicts aspects of the system of FIG. 52.

FIG. 55 illustrates aspects of the system of FIG. 52.

FIG. 56 shows aspects of the system of FIG. 52.

FIG. 57 depicts aspects of the system of FIG. 52.

FIG. 58 illustrates aspects of the system of FIG. 52.

FIG. 59 shows aspects of the system of FIG. 52.

FIG. 60 depicts aspects of the system of FIG. 52.

FIG. 61 illustrates aspects of the system of FIG. 52.

FIG. 62 shows aspects of the system of FIG. 52.

FIG. 63 depicts a system including computer-readable storage mediumincluding executable instructions for monitoring medication events.

FIG. 64 illustrates a flowchart of a method for monitoring medicationevents.

FIG. 65 shows a system for monitoring medication events.

FIG. 66 shows aspects of the system of FIG. 65.

FIG. 67 depicts aspects of the system of FIG. 65.

FIG. 68 illustrates aspects of the system of FIG. 65.

FIG. 69 shows aspects of the system of FIG. 65.

FIG. 70 depicts aspects of the system of FIG. 65.

FIG. 71 illustrates aspects of the system of FIG. 65.

FIG. 72 shows aspects of the system of FIG. 65.

FIG. 73 depicts aspects of the system of FIG. 65.

FIG. 74 illustrates aspects of the system of FIG. 65.

FIG. 75 shows aspects of the system of FIG. 65.

FIG. 76 depicts aspects of the system of FIG. 65.

FIG. 77 illustrates aspects of the system of FIG. 65.

FIG. 78 depicts a system including computer-readable storage mediumincluding executable instructions for monitoring medication events.

FIG. 79 illustrates a flowchart of a method for monitoring medicationevents.

FIG. 80 shows a system for monitoring medication events.

FIG. 81 shows aspects of the system of FIG. 80.

FIG. 82 depicts aspects of the system of FIG. 80.

FIG. 83 illustrates aspects of the system of FIG. 80.

FIG. 84 shows aspects of the system of FIG. 80.

FIG. 85 depicts aspects of the system of FIG. 80.

FIG. 86 illustrates aspects of the system of FIG. 80.

FIG. 87 shows aspects of the system of FIG. 80.

FIG. 88 depicts aspects of the system of FIG. 80.

FIG. 89 illustrates aspects of the system of FIG. 80.

FIG. 90 shows aspects of the system of FIG. 80.

FIG. 91 depicts aspects of the system of FIG. 80.

FIG. 92 illustrates aspects of the system of FIG. 80.

FIG. 93 shows aspects of the system of FIG. 80.

FIG. 94 depicts aspects of the system of FIG. 80.

FIG. 95 shows a system including computer-readable storage mediumincluding executable instructions for monitoring medication events.

FIG. 96 illustrates a flowchart of a method for monitoring medicationevents.

FIG. 97 depicts a system including computer-readable storage mediumincluding executable instructions for monitoring medication events.

FIG. 98 illustrates a flowchart of a method for monitoring medicationevents.

FIG. 99 shows a system for monitoring medication events relating to anindividual.

FIG. 100 depicts a system for monitoring medication events relating toan individual.

FIG. 101 shows a system including computer-readable storage mediumincluding executable instructions for monitoring medication eventsrelating to an individual.

FIG. 102 illustrates a flowchart of a method for monitoring medicationevents relating to an individual.

DETAILED DESCRIPTION

In the following detailed description, reference is made to theaccompanying drawings, which form a part hereof. In the drawings,similar symbols typically identify similar components, unless contextdictates otherwise. The illustrative embodiments described in thedetailed description, drawings, and claims are not meant to be limiting.Other embodiments may be utilized, and other changes may be made,without departing from the spirit or scope of the subject matterpresented here.

The state of the art has progressed to the point where there is littledistinction left between hardware, software, and/or firmwareimplementations of aspects of systems; the use of hardware, software,and/or firmware is generally (but not always, in that in certaincontexts the choice between hardware and software can becomesignificant) a design choice representing cost vs. efficiency tradeoffs.There are various vehicles by which processes and/or systems and/orother technologies described herein can be effected (e.g., hardware,software, and/or firmware), and that the preferred vehicle will varywith the context in which the processes and/or systems and/or othertechnologies are deployed. For example, if an implementer determinesthat speed and accuracy are paramount, the implementer may opt for amainly hardware and/or firmware vehicle; alternatively, if flexibilityis paramount, the implementer may opt for a mainly softwareimplementation; or, yet again alternatively, the implementer may opt forsome combination of hardware, software, and/or firmware. Hence, thereare several possible vehicles by which the processes and/or devicesand/or other technologies described herein may be effected, none ofwhich is inherently superior to the other in that any vehicle to beutilized is a choice dependent upon the context in which the vehiclewill be deployed and the specific concerns (e.g., speed, flexibility, orpredictability) of the implementer, any of which may vary. The opticalaspects of implementations will typically employ optically-orientedhardware, software, and or firmware.

In some implementations described herein, logic and similarimplementations may include software or other control structures.Electronic circuitry, for example, may have one or more paths ofelectrical current constructed and arranged to implement variousfunctions as described herein. In some implementations, one or moremedia may be configured to bear a device-detectable implementation whensuch media hold or transmit device detectable instructions operable toperform as described herein. In some variants, for example,implementations may include an update or modification of existingsoftware or firmware, or of gate arrays or programmable hardware, suchas by performing a reception of or a transmission of one or moreinstructions in relation to one or more operations described herein.Alternatively or additionally, in some variants, an implementation mayinclude special-purpose hardware, software, firmware components, and/orgeneral-purpose components executing or otherwise invokingspecial-purpose components. Specifications or other implementations maybe transmitted by one or more instances of tangible transmission mediaas described herein, optionally by packet transmission or otherwise bypassing through distributed media at various times.

Implementations may include executing a special-purpose instructionsequence or invoking circuitry for enabling, triggering, coordinating,requesting, or otherwise causing one or more occurrences of thefunctional operations described herein. In some variants, operational orother logical descriptions herein may be expressed as source code andcompiled or otherwise invoked as an executable instruction sequence. Insome contexts, for example, implementations may be provided, in whole orin part, by source code, such as C++, or other code sequences. In otherimplementations, source or other code implementation, using commerciallyavailable and/or techniques in the art, may becompiled//implemented/translated/converted into a high-level descriptorlanguage (e.g., initially implementing described technologies in C orC++ programming language and thereafter converting the programminglanguage implementation into a logic-synthesizable languageimplementation, a hardware description language implementation, ahardware design simulation implementation, and/or other such similarmode(s) of expression). For example, some or all of a logical expression(e.g., computer programming language implementation) may be manifestedas a Verilog-type hardware description (e.g., via Hardware DescriptionLanguage (HDL) and/or Very High Speed Integrated Circuit HardwareDescriptor Language (VHDL)) or other circuitry model which may then beused to create a physical implementation having hardware (e.g., anApplication Specific Integrated Circuit).

Logic gates may be arranged to form logic circuits, which are typicallyphysical devices that may be electrically, mechanically, chemically, orotherwise driven to create a physical reality of certain logicalfunctions. Types of logic circuits include such devices as multiplexers,registers, arithmetic logic units (ALUs), computer memory, etc., eachtype of which may be combined to form yet other types of physicaldevices, such as a central processing unit (CPU)—the best known of whichis the microprocessor. A modern microprocessor will often contain morethan one hundred million logic gates in its many logic circuits (andoften more than a billion transistors). See, e.g., Wikipedia, Logicgates, http://en.wikipedia.org/wiki/Logic_gates (as of Jun. 5, 2012,21:03 GMT).

The logic circuits forming the microprocessor are arranged to provide amicroarchitecture that will carry out the instructions defined by thatmicroprocessor's defined Instruction Set Architecture. The InstructionSet Architecture is the part of the microprocessor architecture relatedto programming, including the native data types, instructions,registers, addressing modes, memory architecture, interrupt andexception handling, and external Input/Output. See, e.g., Wikipedia,Computer architecture,http://en.wikipedia.org/wiki/Computer_architecture (as of Jun. 5, 2012,21:03 GMT). The Instruction Set Architecture includes a specification ofthe machine language that can be used by programmers to use/control themicroprocessor. Since the machine language instructions are such thatthey may be executed directly by the microprocessor, typically theyconsist of strings of binary digits, or bits. For example, a typicalmachine language instruction might be many bits long (e.g., 32, 64, or128 bit strings are currently common). A typical machine languageinstruction might take the form “11110000101011110000111100111111” (a 32bit instruction). Machine language is typically incomprehensible by mosthumans (e.g., the above example was just ONE instruction, and somepersonal computers execute more than two billion instructions everysecond).

It is significant here that, although the machine language instructionsare written as sequences of binary digits, in actuality those binarydigits specify physical reality. For example, if certain semiconductorsare used to make the operations of Boolean logic a physical reality, theapparently mathematical bits “1” and “0” in a machine languageinstruction actually constitute a shorthand that specifies theapplication of specific voltages to specific wires. For example, in somesemiconductor technologies, the binary number “1” (e.g., logical “1”) ina machine language instruction specifies around +5 volts applied to aspecific “wire” (e.g., metallic traces on a printed circuit board) andthe binary number “0” (e.g., logical “0”) in a machine languageinstruction specifies around −5 volts applied to a specific “wire.” Inaddition to specifying voltages of the machines' configuration, suchmachine language instructions also select out and activate specificgroupings of logic gates from the millions of logic gates of the moregeneral machine. Thus, far from abstract mathematical expressions,machine language instruction programs, even though written as a stringof zeros and ones, specify many, many constructed physical machines orphysical machine states.

The herein described components (e.g., operations), devices, objects,and the discussion accompanying them are used as examples for the sakeof conceptual clarity and that various configuration modifications arecontemplated. Consequently, as used herein, the specific exemplars setforth and the accompanying discussion are intended to be representativeof their more general classes. In general, use of any specific exemplaris intended to be representative of its class, and the non-inclusion ofspecific components (e.g., operations), devices, and objects should notbe taken as limiting. For example, in some embodiments the systems andmethods described herein can be implemented as a computer programproduct comprising an article of manufacture and bearing instructions.For example, in some embodiments the systems and methods describedherein can be implemented as computer architecture comprising at leastone level. For example, in some embodiments the systems and methodsdescribed herein can be implemented as a device specified bycomputational language. The logical operations/functions set forth inthe present technical description are representative of static orsequenced specifications of various ordered-matter elements, in orderthat such specifications may be comprehensible to the human mind andadaptable to create many various hardware configurations. The logicaloperations/functions disclosed herein should be treated as such.

The systems and methods described herein are intended for use to monitormedication compliance for individuals who have received instructions totake one or more medications as part of a medication regimen under thecare of a medical professional. The systems and methods described hereinmay also be useful for individuals who have a history of non-compliancewith medication regimens to confirm their adherence to the regimen. Thesystems and methods described herein can assist to ensure that theindividual has complied with the medication regimen instructions, forexample with the instructions for dosages and times of administration.The systems and methods described herein can also assist to ensure thatthe individual has complied with the medication regimen instructions,for example in response to a medical event that would indicate medicalintervention is appropriate (e.g. labored breathing indicating apotential asthma event, or unsteady gait indicating dizziness and alikelihood of a fainting event). The systems and methods describedherein can also assist to ensure that the individual has complied withthe medication regimen instructions, for example in response to acurrent medical impairment (e.g. instructions to take a medication inresponse to wheezing when breathing). The systems and methods describedherein can also assist to ensure that the individual has complied withthe medication regimen instructions, for example in response to imminentmedical impairment (e.g. instructions to take a medication in responseto tremors indicating the onset of a seizure).

The combination of recording visual as well as non-visual data over theperiod of the medication event can also assist with detection ofintentional “spoofing,” or attempts to by an individual to make therecord appear that they have taken their medication when in fact theyhave not. The combination of visual data (e.g. an individual puttingpills in his or her mouth) as well as non-visual data (e.g. the sound ofswallowing, or the thermal change in the throat as the medication isswallowed) can provide additional support for compliance with amedication regimen.

Monitoring data obtained from the methods and systems described hereincan be integrated into a health record or a health history for theindividual, for example for later review by a health care provider orfor insurance purposes. The monitoring data described herein includes acombination of visual data (such as generated by a camera) andnon-visual data (such as audio data, thermal data, near-IR data, MIRdata or RF data) over the time of the medication event to ensure that afull record is captured and recorded of the individual taking themedication.

In some embodiments, methods and systems described herein can include analert system, wherein a caregiver is notified when the system does notreceive data indicating that an individual has taken his or hermedication on time. In some embodiments, methods and systems describedherein can include an alert system, wherein a caregiver is notified whenthe system does not receive data indicating that an individual has takenhis or her medication in response to a specific medical event, such aswheezing, unsteady gait, or fever. In some situations, a lack ofcompliance with a medication regimen can have serious healthimplications for an individual, and a caregiver can be notified tointervene. Such systems may be helpful, for example, for individuals whohave periods of confusion and may need to be reminded with a phone callfrom a caregiver or other means to ensure compliance with theirmedication regimen. In some embodiments, methods and systems describedherein can include an alert system, wherein the individual is remindedwhen it is time for a medication. This may be helpful for individualswho have periods of confusion or forgetfulness.

For a more complete understanding, reference now is made to thefollowing descriptions taken in connection with the accompanyingdrawings. The use of the same symbols in different drawings typicallyindicates similar or identical drawings, unless context indicatesotherwise. With reference now to FIG. 1, shown is an example thatillustrates aspects of a system for monitoring medication eventsrelating to an individual that may serve as a context for introducingone or more processes and/or devices described herein. The descriptionof FIG. 1 can be applied, for example, as a context for the descriptionof FIGS. 2-102 herein. In some embodiments, the systems and methodsdescribed herein can be utilized by an individual to record and documenthis or her compliance with a medication regimen (e.g. for insurancereimbursement purposes or as part of an individual medical record). Insome embodiments, the systems and methods described herein can beutilized by an insurance provider to confirm medication compliance. Insome embodiments, the systems and methods described herein can beutilized by researchers to obtain data regarding medication compliancefor patients with particular diagnoses or types of medication regimens.In some embodiments, the systems and methods described herein can beutilized by a medical caregiver team to confirm and document complianceof an individual with a medication regimen. In some embodiments, thesystems and methods described herein can be utilized by a medicalcaregiver team to ensure that a patient has complied with a medicationregimen. In some embodiments, the systems and methods described hereincan be utilized by a medical caregiver team to ensure a complete medicalrecord of an individual patient's medication history. In someembodiments, the systems and methods described herein can be utilized bya medical caregiver team to record medication compliance by a patientwhen there is a possibility of medication overdose, underdose, ormultiple drug interactions. Monitoring of medication events can be ofparticular importance when utilized with patients with specific medicalissues, such as psychosis, memory loss, or sensitivities to high or lowmedication levels. Monitoring of medication events can be important toconfirm that an appropriate medication regimen has been followed by anindividual exhibiting physical symptoms of a medical need. For example,wheezing can indicate a need for asthma medication. For example, bloodpressure changes can indicate a need for diuretics. For example, anunsteady gait can indicate a need for anti-seizure medication.

In some embodiments, an individual has predetermined individualizedmedication intervention parameters accessible to the system thatindicate when a medication event is required as part of a medicationregimen for that individual. The medication intervention parameters caninclude those that indicate a specific physiologic condition of theindividual, which the medical caregiver has determined require amedication event as part of the medication regimen. The medicationintervention parameters can include specific physical symptoms orindicators that a medication event is necessary for a particularindividual. For example, an asthmatic individual can have medicationintervention parameters that include wheezing for a period of time or toa degree of loudness. For example, an asthmatic individual can havemedication intervention parameters that include levels of and/or ratiosof gasses in exhaled breath, such as nitric oxide, nitric dioxide andcarbon dioxide. See US Patent Application Nos. 2007/0048180 to Gabrielet al., “Nanoelectronic breath analyzer and asthma monitor;”2007/0048181 to Chang et al., “Carbon dioxide nanosensor and respiratoryCO2 monitors;” 2006/0055392 to Passmore et al., “Remotely communicating,battery-powered nanostructure sensor devices;” 2008/0050839 to Suslickand McNamara, “Apparatus and method for detecting lung cancer usingexhaled breath;” and International Application No. PCT/US2007/010836 toGabriel et al., “Nanoelectronic breath analyzer and asthma monitor;”which are each incorporated herein by reference. See also Kuzmych etal., “Carbon nanotube sensors for exhaled breath components,”Nanotechnology 18 (2007), which is incorporated by reference herein. Forexample, an epileptic individual can have medication interventionparameters that include slurring speech, unsteady gait, or falling. Forexample, a diabetic individual can have medication interventionparameters that include dilated pupils, unsteady gait, or falling. Forexample, a diabetic individual can have medication interventionparameters that include acetones and/or ketones in breath. See U.S. Pat.No. 6,841,391 to Lewis et al., “Medical applications of artificialolfactometry;” and U.S. Pat. No. 7,261,857 to Suslick et al.,“Colorimetric artificial nose having an array of dyes and method forartificial olfaction;” as well as US Patent Application No. 2010/0166604to Lim et al., “Colorimetric sensor arrays based on nanoporouspigments,” which are each incorporated herein by reference. For example,an individual with a cardiac or respiratory impairment can havemedication intervention parameters that include blood oxygenation levelsthat indicate hyoxemia.

FIG. 1 illustrates an individual 100 and at least one medication 105associated with the individual 100 and administered to the individual100 as part of a medication regimen including a series of medicationevents. An individual 100 is an individual person who, under the care oroversight of a medical professional, has a pre-established medicationregimen including periodic medication events for one or more medications105. An individual 100 has a medication regimen including periodicmedication events with one or more medications 105. A “medication,” asused herein, refers to a medicinal agent, drug or medicamentadministered to an individual person under the instructions of a medicalprofessional for use in the medical diagnosis, cure, treatment orprevention of disease. For example, a medication can include one or moredrugs formulated in pill, capsule, or liquid forms. For example, amedication can include one or more drugs administered via an inhalerdevice. For example, a medication can include one or more drugsadministered via topical application. For example, a medication caninclude one or more drugs administered via transdermal application, suchas with a transdermal patch. For example, a medication can include orone or more drugs administered via injection, such as with a syringedevice. A medication event can include multiple medications. Amedication event can include multiple medications administered indifferent modalities, for example one or more drugs formulated in pillform as well as one or more drugs administered via topical application.A medication can include one or more medicinal agents available onlyunder the supervision of a medical professional (e.g. prescriptionmedication). For example, a medication can include a medicationprescribed for the treatment of anxiety, pain, mental health issues,heart disease, diabetes, asthma or other respiratory disease, allergy,contraception, infection or cancer. For example, a medication caninclude Cymbalta®, Enbrel®, Actos®, Singulair®, Seroquel®, Abilify®,Advair Diskus®, or Lipitor®. A medication can include one or moremedicinal agents that are generally available (e.g. non-prescription orover-the-counter medication) that are included in the medication regimenby a medical professional. For example, a medication can includeaspirin, ibuprofen, naproxen, dextromethorphan, ephedrine,diphenhydramine, or vitamin supplements. A medication 105 can beself-administered to the individual, such as when an individual takespills, drinks a liquid medicament, or uses an inhaler. The medication105 can be partially administered to the individual with assistance,such as when a second person assists the individual 100 to take pills,drink a liquid medicament, or use an inhaler.

A “medication event,” as used herein, refers to an administration orapplication of a specific dosage of one or more medications to anindividual either by themselves or with assistance as part of amedication regimen. A medication event can include a time window foradministration of one or more medications, such as “daily at 2 PM” or“every 6 hours” wherein the time window starts at those times. Amedication event can be triggered by a specific event for theindividual, such as “administer within 30 minutes of the completion of ameal” or “begin inhaler administration at least 1 hour before the startof strenuous exercise.”

A “medication regimen,” as used herein, is a schedule of medicationevents for an individual. A medication regimen is specified by a medicalprofessional and is directed to a particular individual. For example, amedication regimen can include daily, weekly, or monthly schedules ofmedication dosages and times of administration. A medication regimen caninclude two or more medications, each with their specific instructionsfor dosage amounts and times of administration to an individual. Amedication regimen can include alternate, backup or substituteinstructions. For example, a medication regimen can include instructionssuch as “when medication X is not taken in the first time window foradministration, double the dosage at the next time window.” For example,a medication regimen can include instructions such as “when medication Yis not taken in a time window for administration, take the recommendeddosage within 30 minutes of the end of the next meal.” A medicationregimen can include instructions relative to a secondary event. Forexample, a medication regimen can include instructions for medicationevents contingent on one or more secondary events. For example, amedication regimen can include instructions for medication events aftera particular blood sugar reading for a diabetic. For example, amedication regimen can include instructions for medication events aftera particular blood pressure reading for an individual. For example, amedication regimen can include instructions for medication events aftera patient reports a symptom, such as pain or nausea. A medication eventcan include instructions for medication events in response to aphysiologic indicator. For example, a medication regimen can includeinstructions for medication events after a high breath ketone readingfor an individual. For example, a medication regimen can includeinstructions for medication events after detection of an abnormal heartrhythm. For example, a medication regimen can include instructions formedication events after detection of hyoxemia.

As used herein, “visual information” refers to information derived froma visual source, such as information acquired from a camera. As usedherein, “visual information” can include, for example, informationacquired from a digital camera as one or more images taken in a timeseries. As used herein, “visual information” can include, for example,information acquired from a digital camera using a video function of thecamera. For example, visual information can include the analysis of anindividual's eye pupil characteristics. See U.S. Pat. No. 6,097,295 toGriesinger et al., “Apparatus for Determining the Alertness of aDriver,” and U.S. Pat. No. 7,226,164 to Abourizk et al., “Method andApparatus for Testing Sleepiness,” which are each incorporated herein byreference. Visual information can include information that is the basisof an analysis of facial and body characteristics, such as to monitor anindividual for physical and mental impairment (e.g. increased movement,reduced movement, spasmodic or disordered movement). Similarly, as usedherein, “visual data” includes data that is derived from a detection ofa visual event, such as through a series of camera images or a video.

As used herein, “non-visual information” refers to information derivedfrom a non-visual source, such as information derived from a sound, atemperature, a vibration, a wave in a non-visual frequency, or othernon-visual sources. As used herein, “non-visual information” caninclude, for example, information acquired from a near-IR source. Asused herein, “non-visual information” can include, for example, thermalinformation, such as acquired from a temperature measuring device. Asused herein, “non-visual information” can include, for example,information derived from a radio-frequency identification (RFID) tag andacquired by a reader. The RFID tag can be attached, for example, to anidentification item worn by the patient (i.e. an identification braceletincluding a RFID tag). The RFID tag can be attached, for example, to amedication label or packaging. The RFID tag can be attached, forexample, to the medication itself. See: U.S. Pat. No. 7,616,111 toCovannon et al., titled “System to Monitor the Ingestion of Medicines;”and U.S. Pat. No. 7,782,189 to Spoonhower and Covannon, titled “Systemto Monitor the Ingestion of Medicines,” which are each incorporated byreference herein. As used herein, “non-visual information” can include,for example, information derived from an audio source. As used herein,“non-visual information” can include, for example, information acquiredfrom a micropower impulse radar (MIR). See: “Micropower Impulse Radar,”Azevedo and McEwan, Science and Technology Review, January/February1996, pages 17-29; and US Patent Application Publications No.2004/0249257 and 2004/0249258 to Tupin et al., each titled “Article ofManufacture for Extracting Physiological Data Using Ultra-Wideband Radarand Improved Signal Processing Techniques,” which are all incorporatedby reference herein. As used herein, “non-visual information” caninclude, for example, information derived from a ultra-wideband radarsource. See, for example, US Patent Application Publication No.2009/0227882 to Foo, titled “Ultra Wideband Monitoring Systems andAntennas,” which is incorporated by reference herein. As used herein,“non-visual information” can include, for example, information derivedfrom a reflected electromagnetic signal. See: U.S. Pat. No. 7,272,431 toMcGrath, titled “Remote-Sensing Method and Device;” and U.S. Pat. No.7,811,234 to McGrath, titled “Remote-Sensing Method and Device;” whichare each incorporated by reference herein. As used herein, “non-visualinformation” can include, for example, information derived from an audioor auditory source, such as acquired by a microphone. Audio monitoringof speech can be used to monitor for cognitive, psychiatric, physical,or other impairment. As used herein, “non-visual information” caninclude, for example, information derived from the motion of theindividual, such as acquired by an accelerometer. See Culhane et al.,“Accelerometers in rehabilitation medicine for older adults,” Age andAging 34:556-560 (2005), which is incorporated by reference herein. Asused herein, “non-visual information” can include, for example,information derived from blood oxygenation levels, and acquired byinfrared photometry. See Karlen et al., “The Phone Oximeter,” EMBCUnconference 2011, which is incorporated by reference herein. As usedherein, “non-visual information” can include, for example, informationderived from heart rhythms and rates, and acquired from acoustic andvibrational sensors. See, for example, US Patent Application No.2011/0295127 to Sandler and Mansy, “Vibro-acoustic Detection of CardiacConditions,” which is incorporated by reference herein. As used herein,“non-visual information” can include, for example, information derivedfrom heart rhythms and rates, and acquired from electric potentialsensors. See, for example: US Patent Application No. 2006/0058694 toClark et al., “Electrodynamic Sensors and Applications Thereof;”International Publication Number WO 03/048789 to Clark et al.,“Electrodynamic Sensors and Applications Thereof;” and U.S. Pat. No.7,245,956 to Matthews et al., “Unobtrusive Measurement System forBioelectric Signals,” which are each incorporated herein by reference.See also: Harland et al., “Electric potential probes new directions inthe remote sensing of the human body,” Meas. Sci. Technol. 13: 163-169(2002); and Prance et al., Adaptive electric potential sensors for smartsignal acquisition and processing,” Journal of Physics: ConferenceSeries 76 (2007), which are each incorporated herein by reference. Asused herein, “non-visual information” can include, for example,information derived from heart rhythms and rates, and acquired from anelectromagnetic signal reflected off the individual of interest. See,for example, U.S. Pat. No. 7,272,431 to McGrath, “Remote-sensing Methodand Device,” and US Patent Application Nos. 2004/0123667 to McGrath,“Remote-sensing Method and Device,” and 2008/0045832 to McGrath,“Remote-sensing Method and Device,” which are each incorporated hereinby reference. As used herein, “non-visual information” can include, forexample, information derived from chemicals present in an individual'sbreath and indicating the physiological state of the individual. Forexample, ketones and acetone have been used as indicators of an insulininsufficiency in diabetic individuals. A sensor configured to acquireinformation regarding specific breath components of an individual at agiven time can be utilized by the system as an indicator ofphysiological distress. See, for example, U.S. Pat. No. 6,841,391 toLewis et al., “Medical Applications of Artificial Olfactometry,” andU.S. Pat. No. 7,261,857 to Suslick et al., “Colorimetric Artificial Nosehaving an Array of Dyes and Method for Artificial Olfaction,” as well asUS Patent Application No. 2010/0166604, to Lim et al., “ColorimetricSensor Arrays Based on Nanoporous Pigments,” which are each incorporatedby reference herein. Also by way of example, levels of nitric oxide,nitric dioxide and carbon dioxide, as well as the ratios fo thesegasses, have been used as indicators of an imminent asthma attack insome at-risk individuals. A sensor configured to acquire informationregarding specific breath components of an individual at a given timecan be utilized by the system as an indicator of physiological risk.See, for example: US Patent Application Nos. 2007/0048180 to Gabriel etal., “Nanoelectronic breath analyzer and asthma monitor;” 2007/0048181to Chang et al., “Carbon dioxide nanosensor and respiratory CO2monitors;” 2006/0055392 to Passmore et al., “Remotely communicating,battery-powered nanostructure sensor devices;” 2008/0050839 to Suslickand McNamara, “Apparatus and method for detecting lung cancer usingexhaled breath;” and International Application No. PCT/US2007/010836 toGabriel et al., “Nanoelectronic breath analyzer and asthma monitor;”which are each incorporated herein by reference. See also Kuzmych etal., “Carbon nanotube sensors for exhaled breath components,”Nanotechnology 18 (2007), which is incorporated by reference herein.Similarly, as used herein, “non-visual data,” as used herein, refers todata that is acquired from the detection of a non-visual event, such asa sound, a temperature, a vibration, a wave in a non-visual frequency,or other non-visual sources such as those described herein.

There is at least one monitoring device 110 in the area nearby to theindividual 100 during the periodic medication events. The at least onemonitoring device 110 is capable of acquiring visual as well asnon-visual data during the administration of medication 105 to theindividual 100 (i.e. the medication event) and transmitting this data toa computer system 120. The monitoring device can be a dedicated deviceor it can be included as part of a multi-functional device. For example,a monitoring device can include a tablet computer, laptop, smartphone,or similar device. The monitoring device can be a mobile device. Themonitoring device can be a fixed-position device, or a device that isdesigned to be fixed to a particular location. For example, themonitoring device can be a digital camera device configured to beaffixed to a wall. The monitoring device 110 can include at least onecamera unit that is capable of acquiring visual and non-visual data. Forexample, a monitoring device can include a portable computing deviceincluding a camera unit that can acquire data from the near-infrared(IR) spectrum as well as the visual spectrum. For example, a monitoringdevice can include a portable computing device including a camera unitand a microphone unit. For example, a monitoring device can include aportable computing device including a camera unit and a RFIDtransceiver. In some embodiments, the at least one monitoring device 110can also include other features, such as a keyboard 160 and a screen155. In some embodiments, there are a plurality of monitoring devices.

A monitoring device 110 processes the visual and non-visual dataacquired during a medication event and transmits processed informationto a computer system 120. In some embodiments, at least one monitoringdevice 110 transmits signals 115 via wireless communication to acomputer system 120. In some embodiments, at least one monitoring device110 transmits signals 115 via a wired connection to a computer system120. In some embodiments, the at least one monitoring device 110 isconfigured to receive signals 150 transmitted from the computer system120. In some embodiments, at least one monitoring device 110 isconfigured to receive signals 150 transmitted from the computer system120 via wireless communication. In some embodiments, at least onemonitoring device 110 is configured to receive signals 150 transmittedfrom the computer system 120 via a wired connection. For example, the atleast one monitoring device 110 can be configured to receivetransmission signals 150 over a telephone wire, an optical fiber cable,or a dedicated signal transmission wire.

A system 120 includes one or more computing devices functionallyintegrated to operate together. For example, a system 120 can includeone or more main computing units 125 as well as one or more secondarycomputing units 130. A system 120 can include one or more secondarycomputing units 130 configured to be operable by a user 140, such as amember of the medical caregiver team. A system 120 can include one ormore mobile computing devices 135 configured to be operable by a user145, such as a member of the medical caregiver team. Although users 140,145 is shown/described herein as a single illustrated figure, users 140,145 may be representative of a human user, a robotic user (e.g.,computational entity), and/or substantially any combination thereof(e.g., a user may be assisted by one or more robotic agents) unlesscontext dictates otherwise. In general, the same may be said of “sender”and/or other entity-oriented terms as such terms are used herein unlesscontext dictates otherwise. A mobile computing device 135 can beintegrated with a multipurpose mobile computing device, such as asmartphone, PDA, tablet or communication device. The computing devices125, 130, 135 of a system 120 are configured to be able to send andreceive information in the form of signals between the computing devices125, 130, 135. The computing devices 125, 130, 135 of a system 120 caninclude input devices, such as keyboards, computer mice, or touchpads.The computing devices 125, 130, 135 of a system 120 can include devicesto present results visually to a system user 140, 145 such as monitors,lights, or displays. The computing devices 125, 130, 135 of a system 120can include devices that present results or alert system users 140, 145of results through non-visual means, such as buzzers, speakers, andvibratory elements. In some embodiments, there may be a dedicated alertdevice, such as a light or audible alarm, attached to the computersystem 120. The computing devices 125, 130, 135 of a system 120 caninclude memory devices integral to or attached. For example, a maincomputing unit 125 or a secondary computing unit 130, 135 can includeinternal computer memory. For example, a main computing unit 125 or asecondary computing unit 130, 135 can be attached to an additionaldevice configured to store computer memory. The computer system 120 caninclude one or more transmission devices, including, for example,transmitters, receivers, or transceivers. The transmission devices ofthe system 120 can be configured to transmit and receive informationbetween components of the system (e.g. a main computing unit 125 and asecondary computing unit 135) or to another device (e.g. a monitoringdevice 110).

An individual 100, such as shown in FIG. 1, has a personalizedmedication regimen preset by one or more members of the medicalcaregiver team (e.g. users 140 and 145). The medication regimen includesinstructions for the administration of a specific dose of a medication105 at a particular time or within a time window, or a medication event.At least one monitoring device 110 is positioned in the vicinity of theindividual 100 at an orientation and distance to generate both visualand non-visual data regarding the medication event. In some embodiments,the individual 100 can operate the at least one monitoring device 110,such as turning it on, positioning it, etc. In some embodiments, theindividual 100 does not operate the at least one monitoring device 110.For example, the monitoring device 110 may be a fixed-position devicethat is not turned on and off by the individual 100.

FIG. 2 illustrates further aspects of the systems and methods describedherein. FIG. 2 illustrates diagram of aspects of a system for monitoringmedication events relating to an individual. The system can be acomputer system such as depicted in FIG. 1 and described herein. Thesystem 200 depicted in FIG. 2 includes electrical circuitry. Thecircuitry of the system 200 is configured to carry out a series oflogical processes. As illustrated in FIG. 2, a system 200 for monitoringmedication events relating to an individual includes one or morecircuitry components 210, 220, 230, 240, 250, 260, 270, 280. Thecircuitry is configured to carry out specific processes.

The system 200 includes circuitry 210 for analyzing received data for anidentifier of a first medication event for an individual. An identifierof a first medication event is a predetermined identifier of themedication event. For example, the system can analyze received data fora personal identifier, such as a name, patient ID number, or identifyingcode. For example, the system can analyze received data for a visuallyapparent identifier, such as a bar code, a matrix barcode, or visualfeatures of a medication label. For example, the system can analyzereceived data for a non-visually apparent identifier, such as a auditorysignal like the individual stating his or her medication, the individualstating a specific phrase, such as “I am taking my medication now,” or aparticular sound. For example, the system can analyze received data fora non-visually apparent identifier, such as a RFID identifier specificto a medication label. In some embodiments, there can be more than oneidentifier of a first medication event for an individual. For example,the system can be preset to recognize either a bar code or a RFIDidentifier specific to a medication label as an identifier. In someembodiments, there can be a combination of features to form theidentifier of a first medication event for an individual. For example,the identifier can include visual data from a bar code on the medicationlabel in combination with auditory data including the individual stating“I am taking my medication now.”

The system 200 includes circuitry 220 for analyzing the received datafor at least one attribute of the individual. An “attribute of theindividual,” as used herein, is a predetermined attribute identifiableby the system in the received data that identifies the specificindividual(s) detected by the monitoring device and included in thetransmitted data from the monitoring device. For example, an attributeof the individual can include a visually apparent aspect of theindividual to whom the medication is administered, such as aspects ofthe facial features of the individual. For example, an attribute of theindividual can include a non-visually apparent aspect of the individualto whom the medication is administered, such as a code identifier from akeypad or other input device. For example, an attribute of theindividual can include audio data of the individual stating his or hername. For example, an attribute of the individual can include a RFIDcode from an object associated with the individual (such as a card orbracelet) and scanned by a monitoring device. For example, an attributeof the individual can include an image of a fingerprint of theindividual. For example, an attribute of the individual can includefacial attributes (e.g. eye color, distance between eyes, nose shape,etc.) or other biometric attributes. In some embodiments, there can bemore than one attribute of the individual. For example, the system canbe preset to recognize either a bar code or a RFID identifier specificto an individual's identification card or tag as an attribute associatedwith the individual by the system. In some embodiments, there can be acombination of features to form the attribute of the individual. Forexample, an attribute of the individual can include visual data from abar code on a patient ID tag in combination with auditory data includingthe individual stating his or her name.

The system 200 includes circuitry 230 for analyzing the received datafor at least one attribute relating to a medication during the firstmedication event. An attribute relating to a medication during the firstmedication event is an predetermined attribute of the medication that isdetected during the first medication event. For example, an attributerelating to a medication during the first medication event can include avisual aspect of the medication, such as pill color, in combination withtime data that identifies the attribute of the medication as detectedduring the first medication event.

The system 200 includes circuitry 240 for analyzing the received datafor at least one feature of visual information relating to theindividual during the first medication event. A feature of visualinformation relating to the individual during the first medication eventis an predetermined feature of visual information relating to theindividual that is detected during the first medication event. Forexample, a feature of visual information can include visual images ofthe individual placing one or more pills into his or her mouth and thenswallowing the pills, in combination with time data. For example, afeature of visual information can include visual images of theindividual placing an inhaler in his or her mouth and activating theinhaler, in combination with time data.

The system 200 includes circuitry 250 for analyzing the received datafor at least one feature of non-visual information relating to theindividual during the first medication event. A feature of non-visualinformation relating to the individual during the first medication eventis an predetermined feature of non-visual information relating to theindividual that is detected during the first medication event. Forexample, a feature of non-visual information can include the sounds ofthe individual swallowing the pills, in combination with time data. Forexample, a feature of visual information can include auditory data ofthe individual placing an inhaler in his or her mouth and activating theinhaler, in combination with time data.

The system 200 includes circuitry 260 for analyzing the received datafor a time associated with the first medication event. A time associatedwith a medication event is a predetermined time within a time window aspart of a preset medication regimen. For example, a time associated witha medication event can be a time within a time window of when themedication event should occur in accord with the medication regimen. Forexample, the time associated with a medication event can be a clocktime, such as “between 4 and 430 PM.” For example, the time associatedwith a medication event can be a relative time, such as “3 to 4 hoursafter the end of the last medication event.”

The system 200 includes circuitry 270 for determining a compliancelikelihood for the first medication event based on the analyses of thereceived data. The standards for determining a compliance likelihood arepredetermined and specific to a particular medication event or type ofmedication events for an individual. For example, a compliancelikelihood can be determined from a series of binary indicatorsregarding the analyses of the circuitry previously described, 210, 220,230, 240, 250, 260. For example, a compliance likelihood can bedetermined from a table of attributes and features of the medication,the individual, and the medication event that should be present in dataobtained by the monitoring device during a medication regimen compliantmedication event. For example, if all attributes and features of themedication, the individual, and the medication event are present in thedata from the monitoring device, the compliance likelihood can bedetermined to be high, with a value such as 1 or 100%. For example, ifall attributes and features of the medication, the individual, and themedication event are not present in the data from the monitoring device,the compliance likelihood can be determined to be less than high, orless than 1 or less than 100%.

The system 200 includes circuitry 280 for indicating the determinedcompliance likelihood for the first medication event. For example, thecircuitry can be configured to indicate the determined compliancelikelihood on the display of a computing device that is part of thesystem (e.g. the remote device 135 of FIG. 1).

FIG. 3 illustrates other aspects of the system 200 depicted in FIG. 2.As shown in FIG. 3, in some embodiments the circuitry 210 for analyzingreceived data for an identifier of a first medication event for anindividual includes additional aspects. FIG. 3 illustrates that in someembodiments the circuitry 210 for analyzing received data for anidentifier of a first medication event for an individual includescircuitry 300 for analyzing received data encoded in a transmissionoriginating from a cell phone. For example, a cell phone can be utilizedby the individual as a monitoring device (e.g. monitoring device 110 ofFIG. 1) to obtain visual and non-visual data during the first medicationevent. Subsequently, the data regarding the medication event can betransmitted from the cell phone to the system for processing andanalysis. The system can include circuitry 300 for analyzing thereceived data encoded in a transmission originating from the cell phone.FIG. 3 also shows that in some embodiments the circuitry 210 foranalyzing received data for an identifier of a first medication eventfor an individual can include circuitry 310 for analyzing received dataencoded in a transmission originating from a portable computing device.For example, a portable computing device, such as a laptop, tablet, orPDA, can be utilized by the individual as a monitoring device (e.g.monitoring device 110 of FIG. 1) to obtain visual and non-visual dataduring the first medication event. Subsequently, the data regarding themedication event can be transmitted from the portable computing deviceto the system for further data processing and analysis. The system caninclude circuitry 310 for analyzing the received data encoded in atransmission originating from the portable computing device. FIG. 3depicts that the circuitry 210 for analyzing received data for anidentifier of a first medication event for an individual can include, insome embodiments, circuitry 320 for analyzing received data encoded in atransmission from a fixed position camera unit. For example, a fixedposition camera unit can be affixed to a wall or furnishing. A fixedposition camera unit can be configured as a monitoring device (e.g.monitoring device 110 of FIG. 1) to obtain visual and non-visual dataduring the first medication event. For example, the fixed positioncamera unit can be configured to turn on at the appropriate times toobtain data regarding a medication event. Data obtained from a fixedposition camera unit can be processed and transmitted to the system 200for monitoring medication events relating to an individual. FIG. 3 showsthat, in some embodiments, the circuitry 210 for analyzing received datafor an identifier of a first medication event for an individual caninclude circuitry 330 for analyzing received data for an identifier thatincludes a code. For example, the circuitry 210 for analyzing receiveddata for an identifier of a first medication event for an individual caninclude circuitry 330 for analyzing received data for an identifier thatincludes a code such as an RFID code, a patient identification code, acode identifying the source of the data (e.g. a cell phone number orlocation code for a fixed position camera unit) or other codes. Anidentifier that includes a code can include an identifier of the sourceof the data (e.g. a cell phone or a fixed position camera unit). Anidentifier that includes a code can include an identifier of theindividual, for example a patient ID code or a RFID code associated withthe individual. An identifier that includes a code can include anidentifier of the medication event, such as a code identifying thespecific type of medication event. An identifier that includes a codecan include an identifier of the medication, such as a Q code scannedfrom the medication label. The code can include an alphanumeric code, abinary code, or other types of codes. FIG. 3 depicts that, in someembodiments, the circuitry 210 for analyzing received data for anidentifier of a first medication event for an individual can includecircuitry 340 for analyzing the received data for an identifier thatincludes at least one visual information feature. For example, thecircuitry 340 for analyzing the received data for an identifier thatincludes at least one visual information feature can include circuitryfor identifying a visual information feature of the medication, such asthe shape and color of a specific type of pills, or the label from amedication container. For example, the circuitry 340 for analyzing thereceived data for an identifier that includes at least one visualinformation feature can include circuitry for identifying a visualinformation feature of the individual, such as facial aspects, coloring,or visual aspects of a tag worn by the individual. For example, thecircuitry 340 for analyzing the received data for an identifier thatincludes at least one visual information feature can include circuitryfor identifying a temporal visual information feature, such as theidentification of a time from the visual information of a wall clock.

FIG. 4 illustrates other aspects of the system 200 depicted in FIG. 2.As shown in FIG. 4, in some embodiments the circuitry 210 for analyzingreceived data for an identifier of a first medication event for anindividual can include circuitry 400 for analyzing the received data foran identifier that includes at least one non-visual information feature.For example, the identifier of a first medication event can include anidentifier that includes an identifier with audio information. Forexample, an identifier of a first medication event for the individualthat includes at least one non-visual information feature can includeaspects of an audio recording of the individual saying “I am taking mymedication now.” For example, an identifier of a first medication eventfor the individual that includes at least one non-visual informationfeature can include aspects of an audio recording of a tone, beep orother sound originating from the monitoring device (e.g. 110 in FIG. 1).For example, an identifier of a first medication event for theindividual that includes at least one non-visual information feature caninclude aspects of an audio recording of a sound from a medicationadministration device, such as an inhaler being used. For example, theidentifier of a first medication event can include an identifier thatincludes an identifier with near-IR information. For example, anidentifier of a first medication event for the individual that includesat least one non-visual information feature can include aspects of thenear-IR readings of an individual's throat as he or she is swallowing amedication.

FIG. 4 also depicts that, in some embodiments, the circuitry 210 foranalyzing received data for an identifier of a first medication eventfor an individual can include circuitry 410 for analyzing the receiveddata for a radio-frequency identification (RFID) code. For example, theidentifier of a first medication event can include an identifier thatincludes an identifier such as an RFID code that the system canassociate with the medication event.

FIG. 4 further illustrates that, in some embodiments, circuitry 220 foranalyzing the received data for at least one attribute of an individualincludes circuitry 420. Circuitry 420 includes: circuitry forassociating the identifier of the first medication event with anexpected individual; circuitry for retrieving one or more specificidentifiers associated with the expected individual; circuitry foranalyzing the received data for the presence or absence of at least oneof the one or more specific identifiers; and circuitry for indicatingthe presence or absence of the expected individual based on theanalysis. For example, circuitry 420 can include circuitry forassociating the identifier of the first medication event with anexpected individual; circuitry for retrieving one or more specificidentifiers associated with the expected individual, such as visualidentifiers of the individual's body or face; circuitry for analyzingthe received data for the presence or absence of at least one of the oneor more specific identifiers of the individual's body or face; andcircuitry for indicating the presence or absence of the expectedindividual based on the analysis. For example, if visual identifiers ofthe expected individual's face are not present in the received data, thecircuitry can indicate the absence of the expected individual. Forexample, circuitry 420 can include circuitry for associating theidentifier of the first medication event with an expected individual;circuitry for retrieving one or more specific identifiers associatedwith the expected individual, such as an identification code that wasentered onto the keypad of a monitoring device; circuitry for analyzingthe received data for the presence or absence of at least one of the oneor more specific identifiers of the expected individual, such as apersonal identification code; and circuitry for indicating the presenceor absence of the expected individual based on the analysis.

FIG. 5 illustrates further aspects of the system 200 shown in FIG. 2.FIG. 5 depicts that, in some embodiments, circuitry 220 for analyzingthe received data for at least one attribute of an individual includescircuitry 500. Circuitry 500 includes circuitry for associating theidentifier of the first medication event with an expected medication;circuitry for retrieving one or more attributes associated with theexpected medication; circuitry for comparing the retrieved one or moreattributes associated with the expected medication with the receiveddata; circuitry for determining, based on the comparison, a confirmationlikelihood for the expected medication; and circuitry for indicating thedetermined confirmation likelihood for the expected medication. Forexample, in some embodiments, circuitry 500 can include circuitry forassociating the identifier of the first medication event with anexpected medication; circuitry for retrieving one or more attributesassociated with the expected medication, such as visual attributes ofpill color and shape; circuitry for comparing the retrieved one or moreattributes associated with the expected medication with the receiveddata; circuitry for determining, based on the comparison, a confirmationlikelihood for the expected medication; and circuitry for indicating thedetermined confirmation likelihood for the expected medication. Theconfirmation likelihood can be presented in different forms depending onthe requirements of the embodiment, such as a scale, a percent, anumerical value, a color gradient, or other representation. For example,in some embodiments, circuitry 500 can include circuitry for associatingthe identifier of the first medication event with an expectedmedication; circuitry for retrieving one or more attributes associatedwith the expected medication, such as an expected RFID code from themedication label; circuitry for comparing the retrieved one or moreattributes associated with the expected medication with the receiveddata; circuitry for determining, based on the comparison, a confirmationlikelihood for the expected medication; and circuitry for indicating thedetermined confirmation likelihood for the expected medication. FIG. 6shows further aspects of the system 200 shown in FIG. 2. FIG. 6illustrates that, in some embodiments, circuitry 220 for analyzing thereceived data for at least one attribute of an individual includescircuitry 600 for analyzing the received data for at least one attributeof the individual; circuitry for comparing the at least one attribute ofthe individual with a set of attribute parameters for an expectedindividual; and circuitry for determining, based on the comparison, anattribute score for the at least one attribute of the individual. Forexample, in some embodiments the circuitry 220 for analyzing thereceived data for at least one attribute of an individual can includecircuitry 600 for analyzing the received data for at least one attributeof the individual, such as visual attributes of facial structure;circuitry for comparing the at least one visual attributes of facialstructure of the individual with a set of parameters for visualattributes of facial structure for an expected individual; and circuitryfor determining, based on the comparison, an attribute score for thevisual attributes of facial structure of the individual. For example,the circuitry 600 can be configured to compare eye color, distancebetween eye sockets, nose shape, and other visual facial features with aset of parameters for visual attributes of facial structure for anexpected individual. The system can also include circuitry fordetermining, based on the comparison, an attribute score for the visualattributes of facial structure of the individual and circuitry fordisplaying the determination in a visual format such as a graph, table,numerical score, or other visual format. For example, in someembodiments the circuitry 220 for analyzing the received data for atleast one attribute of an individual can include circuitry 600 foranalyzing the received data for at least one attribute of theindividual, such as audio features of a voice recording; circuitry forcomparing the at least one audio features of a voice recording of theindividual with a set of parameters for audio features of a voicerecording for an expected individual; and circuitry for determining,based on the comparison, an attribute score for the audio features of avoice recording of the individual. For example, the circuitry 600 can beconfigured to compare the tone, cadence, pitch, and other audio featuresof a voice recording with a set of parameters for audio features of avoice recording for an expected individual. The system can also includecircuitry for determining, based on the comparison, an attribute scorefor the audio features of a voice recording of the individual andcircuitry for displaying the determination in a visual format such as agraph, table, numerical score, or other visual format. For example, insome embodiments the circuitry 220 for analyzing the received data forat least one attribute of an individual can include circuitry 600 foranalyzing the received data for at least one attribute of theindividual, such as an identifier code typed onto a touchpad of amonitoring device (e.g. item numbered 110 in FIG. 1); circuitry forcomparing the input identifier code of the individual with a set ofparameters for identifier codes for an expected individual, such as witha look-up table; and circuitry for determining, based on the comparison,an attribute score for the identifier code of the individual. The systemcan also include circuitry for determining, based on the comparison, anattribute score for the identifier code of the individual and circuitryfor displaying the determination in a visual format such as a graph,table, numerical score, or other visual format.

FIG. 7 illustrates aspects of the system 200 shown in FIG. 2. FIG. 7illustrates that, in some embodiments, circuitry 230 for analyzing thereceived data for at least one attribute relating to a medication duringthe first medication event includes circuitry 700 for analyzing thereceived data for an attribute that includes at least one visualinformation feature. For example, the attribute of the medication thatincludes at least one visual information feature can include the colorand shape of the medication delivery device, visual aspects of themedication label, the color and shape of pills or capsules, or othervisual attributes of the medication. FIG. 7 also shows that, in someembodiments, circuitry 230 for analyzing the received data for at leastone attribute relating to a medication during the first medication eventincludes circuitry 710 for analyzing the received data for an attributethat includes at least one non-visual information feature. For example,the circuitry can be configured to analyze the received data for anon-visual attribute such as a RFID code from the medication label, thesound of an inhaler in use, or the near-IR reflection of the medicationlabel or packaging. FIG. 7 further illustrates that, in someembodiments, circuitry 230 for analyzing the received data for at leastone attribute relating to a medication during the first medication eventincludes circuitry 720 analyzing the received data for an attribute thatincludes a radio-frequency identification (RFID) code. For example, amonitoring device (e.g. item numbered 110 in FIG. 1) can be configuredto scan a medication label or packaging with a RF signal, and to accepta return signal with RFID information.

FIG. 8 shows aspects of the system 200 illustrated in FIG. 2. FIG. 8illustrates that, in some embodiments, circuitry 230 for analyzing thereceived data for at least one attribute relating to a medication duringthe first medication event includes circuitry 800 for analyzing thereceived data for at least one attribute of the medication; circuitryfor comparing the at least one attribute of the medication with a set ofattribute parameters for an expected medication; and circuitry fordetermining, based on the comparison, an attribute score for the atleast one attribute of the medication. For example, circuitry 800 caninclude: circuitry configured to analyze the received data for pillcolor and number; circuitry configured to compare the pill color andnumber with a set of attribute parameters for an expected medication,including pill number and color; and circuitry for determining, based onthe comparison, an attribute score for the pill number and color. Thesystem can also include circuitry for displaying the determinedattribute score in a visual format such as a graph, table, numericalscore, or other visual format.

FIG. 9 depicts aspects of the system 200 illustrated in FIG. 2. FIG. 9shows that, in some embodiments, circuitry 230 for analyzing thereceived data for at least one attribute relating to a medication duringthe first medication event includes circuitry 900 for associating theidentifier of the first medication event with an expected medication;circuitry for retrieving one or more specific identifiers associatedwith the expected medication; circuitry for analyzing the received datafor the presence or absence of at least one of the one or more specificidentifiers; and circuitry for indicating the presence or absence of theexpected medication based on the analysis. For example, in someembodiments the circuitry 900 includes circuitry for associating theidentifier of the first medication event, such as visual informationfrom a medication label, with an expected medication; circuitry forretrieving one or more specific identifiers associated with the expectedmedication, such as dispenser shape and size; circuitry for analyzingthe received data for the presence or absence of at least one of the oneor more specific identifiers, such as the dispenser shape or size; andcircuitry for indicating the presence or absence of the expectedmedication based on the analysis. The circuitry for indicating thepresence or absence of the expected medication based on the analysis caninclude circuitry for a graphical indicator, such as a chart, table,text, or graph on a display. The circuitry for indicating the presenceor absence of the expected medication based on the analysis can includecircuitry for a light indicator, such as a green light indicator.

FIG. 10 shows aspects of the system 200 illustrated in FIG. 2. FIG. 10illustrates that, in some embodiments, circuitry 230 for analyzing thereceived data for at least one attribute relating to a medication duringthe first medication event includes circuitry 1000. Circuitry 1000includes: circuitry for associating the identifier of the firstmedication event with an expected medication; circuitry for retrievingone or more attributes associated with the expected medication;circuitry for comparing the retrieved one or more attributes associatedwith the expected medication with the received data; circuitry fordetermining, based on the comparison, a confirmation likelihood for theexpected medication; and circuitry for indicating the determinedconfirmation likelihood for the expected medication. For example,circuitry 1000 can include: circuitry for associating the identifier ofthe first medication event, such as the audio recording of theindividual saying “I am taking medication XYZ now,” with an expectedmedication; circuitry for retrieving one or more attributes associatedwith the expected medication “XYZ,” such as visual aspects of themedication label; circuitry for comparing the retrieved visual aspectsof the medication label associated with the expected medication “XYZ”with the received data; circuitry for determining, based on thecomparison, a confirmation likelihood for the expected medication “XYZ”for the specific medication event; and circuitry for indicating thedetermined confirmation likelihood for the expected medication “XYZ.”For example, circuitry 1000 can include: circuitry for associating theidentifier of the first medication event, such as the visual aspects ofthe medication label, with an expected medication; circuitry forretrieving one or more attributes associated with the expectedmedication, such as expected visual aspects of the medication label;circuitry for comparing the retrieved visual aspects of the medicationlabel associated with the expected medication with the received data;circuitry for determining, based on the comparison, a confirmationlikelihood for the expected medication for the specific medicationevent; and circuitry for indicating the determined confirmationlikelihood for the expected medication. For example, the system can beconfigured to indicate the determined confirmation likelihood for theexpected medication to a medical professional using the system, (e.g.illustrated as 140 and 145 in FIG. 1). The determined confirmationlikelihood can be indicated in a light on/light off format, such as ared light or a green light. The determined confirmation likelihood canbe indicated in a text, graph, or other format. In some embodiments, thesystem can include circuitry for initiating an alarm based on thedetermined confirmation likelihood, such as if the determinedconfirmation likelihood is below a threshold amount. Such circuitry can,for example, serve as a warning system for an individual or medicalcaregivers to indicate that the incorrect medication has beenadministered during the medication event.

FIG. 11 shows aspects of the system 200 depicted in FIG. 2. FIG. 11illustrates that, in some embodiments, circuitry 240 for analyzing thereceived data for at least one feature of visual information relating tothe individual during the first medication event can include circuitry1100. Circuitry 1100 includes: circuitry for identifying a visualinformation component of the received data; circuitry for comparing theidentified visual information component of the received data with atleast one visual information parameter; and circuitry for determining alikelihood of sufficiency for the visual information component of thereceived data based on the comparison. For example, circuitry 1100 caninclude: circuitry for identifying a visual information component of thereceived data, such as facial features; circuitry for comparing theidentified facial features component of the received data with at leastone facial feature parameter; and circuitry for determining a likelihoodof sufficiency for the facial feature component of the received databased on the comparison. For example, the circuitry 1100 can beconfigured to determine the likelihood of sufficiency for the facialfeature component of the received data in order to confirm that theindividual has taken his or her medication (i.e. not “spoofing” themedication event). In some embodiments, circuitry 240 can includecircuitry for indicating the determined likelihood of sufficiency forthe visual information component of the received data to at least onesystem user, (e.g. illustrated as 140 and 145 in FIG. 1). Circuitry forindicating the determined likelihood of sufficiency for the visualinformation component of the received data to at least one system usercan include circuitry for depicting a graph, a table, text, or a lightindicator. The determined likelihood of sufficiency for the visualinformation component of the received data can be utilized by the systemuser, such as a medical caregiver, to determine if the visualinformation component of the medication event is sufficient to ensureaspects of the medication event happened correctly, such as themedication label was identified, the medication was identified, theindividual took the medication correctly, etc.

FIG. 12 shows aspects of the system 200 depicted in FIG. 2. FIG. 12illustrates that, in some embodiments, circuitry 240 for analyzing thereceived data for at least one feature of visual information relating tothe individual during the first medication event can include circuitry1200. Circuitry 1200 includes: circuitry for associating the identifierof the first medication event with a set of visual informationparameters for a standard medication event; circuitry for comparing theat least one feature of visual information relating to the individualduring the first medication event with the set of visual informationparameters for the standard medication event; circuitry for determining,based on the comparison, a medication event compliance score for thefirst medication event; and circuitry for indicating the determinedmedication event compliance score for the first medication event. Forexample, in some embodiments circuitry 1200 can include: circuitry forassociating the identifier of the first medication event, such as visualfeatures of the individual, with a set of visual information parameters,such as visual features of the individual for a standard medicationevent; circuitry for comparing the at least one feature of visualinformation relating to the individual during the first medication eventwith the set of visual information parameters for the standardmedication event; circuitry for determining, based on the comparison, amedication event compliance score for the first medication event; andcircuitry for indicating the determined medication event compliancescore for the first medication event. In some embodiments, the circuitryfor indicating the determined medication event compliance score for thefirst medication event can include circuitry for indicating a graph,table, text score, or other visual indicator.

FIG. 13 shows aspects of the system 200 illustrated in FIG. 2. FIG. 13shows that, in some embodiments, circuitry 250 for analyzing thereceived data for at least one feature of non-visual informationrelating to the individual during the first medication event includesone or more of circuitry 1300, 1310, 1320 and 1330. FIG. 13 illustratesthat circuitry 1300 includes: circuitry for analyzing the received datafor the at least one feature of the non-visual information includingnear-infrared (IR) information. For example, circuitry 1300 can includefor analyzing the received data for near-infrared (IR) informationregarding the medication event. For example, circuitry 1300 can includefor analyzing the received data for near-infrared (IR) informationassociated with the individual's throat during the medication event,which can serve to validate the medication administration such as with apositional shift during swallowing. For example, circuitry 1300 caninclude: circuitry for analyzing the received data for near-infrared(IR) information associated with the individual's skin adjacent toadministration of a medication via syringe during the medication event,which can serve to validate the medication administration such as with askin flush after injection of the medication. FIG. 13 furtherillustrates that circuitry 1310 includes: circuitry for analyzing thereceived data for the at least one feature of the non-visual informationincluding auditory information. For example, in some embodimentscircuitry 1310 can include circuitry for analyzing the received data forauditory information, such as auditory information relating to theindividual swallowing, or using an inhaler. FIG. 13 also shows thatcircuitry 1320 includes: circuitry for analyzing the received data forthe at least one feature of the non-visual information including thermalinformation. For example, in some embodiments circuitry 1320 can includecircuitry for analyzing the received data for thermal informationassociated with the individual's skin adjacent to administration of amedication via syringe during the medication event, which can serve tovalidate the medication administration such as with a temperature shiftafter injection of the medication. For example, in some embodimentscircuitry 1320 can include circuitry for analyzing the received data forthermal information associated with the individual's throat during themedication event, which can serve to validate the medicationadministration such as with a temperature change during swallowing. FIG.13 also depicts that circuitry 250 can include circuitry 1330 foranalyzing the received data for the at least one feature of thenon-visual information including kinetic information. For example,circuitry 1330 can include circuitry for analyzing the received data forkinetic information, such as the movement of a syringe or inhaler duringthe medication event. For example, circuitry 1330 can include circuitryfor analyzing the received data for kinetic information, such as themotion of the individual to place the syringe for medicationadministration.

FIG. 14 shows aspects of the system as illustrated in FIG. 2. FIG. 14shows that, in some embodiments, circuitry 250 for analyzing thereceived data for at least one feature of non-visual informationrelating to the individual during the first medication event includesone or more of circuitry 1400, 1410. Circuitry 1400 includes: circuitryfor analyzing the received data for the at least one feature of thenon-visual information including micropower impulse radar (MIR)information. For example, circuitry 1400 can include circuitry foranalyzing the received data for information including micropower impulseradar (MIR) information, such as MIR information relating to themedication administration to the individual and associated physiologicaleffects. See: “Micropower Impulse Radar,” Azevedo and McEwan, Scienceand Technology Review, January/February 1996, pages 17-29; and US PatentApplication Publications No. 2004/0249257 and 2004/0249258 to Tupin etal., each titled “Article of Manufacture for Extracting PhysiologicalData Using Ultra-Wideband Radar and Improved Signal ProcessingTechniques,” which are all incorporated by reference herein. See also:US Patent Application Publication No. 2009/0227882 to Foo, titled “UltraWideband Monitoring Systems and Antennas,” which is incorporated byreference herein. Circuitry 1410 includes: circuitry for identifying anon-visual information component of the received data; circuitry forcomparing the identified non-visual information component of thereceived data with at least one non-visual information parameter; andcircuitry for determining a likelihood of sufficiency for the non-visualinformation component of the received data based on the comparison. Forexample, some embodiments of the system can include circuitry foridentifying an audio component of the received data; circuitry forcomparing the identified audio component of the received data with atleast one audio information parameter; and circuitry for determining alikelihood of sufficiency for the audio information component of thereceived data based on the comparison. For example, the audioinformation parameter can include a decibel range for audio information,or a signal strength parameter. For example, some embodiments of thesystem can include circuitry for identifying a RFID signal component ofthe received data; circuitry for comparing the identified RFID signalcomponent of the received data with at least one RFID signal parameter;and circuitry for determining a likelihood of sufficiency for the RFIDsignal component of the received data based on the comparison. Forexample, the RFID signal parameter can include a signal strength orsignal quality parameter.

FIG. 15 shows further aspects of the system 200 illustrated in FIG. 2.FIG. 15 shows that, in some embodiments circuitry 250 for analyzing thereceived data for at least one feature of non-visual informationrelating to the individual during the first medication event includes:circuitry 1500 for identifying a non-visual information component of thereceived data; circuitry for comparing the identified non-visualinformation component of the received data with at least one non-visualinformation parameter; and circuitry for determining a likelihood ofsufficiency for the non-visual information component of the receiveddata based on the comparison. For example, circuitry 1500 can includecircuitry for identifying an audio information component of the receiveddata; circuitry for comparing the identified audio information componentof the received data with at least one audio information parameter; andcircuitry for determining a likelihood of sufficiency for the audioinformation component of the received data based on the comparison. Forexample, the at least one audio information parameter can include atleast one of: a duration of the audio information, a decibel minimum andmaximum for the audio information, and a tone range for the audioinformation.

FIG. 16 illustrates further aspects of the system 200 shown in FIG. 2.FIG. 16 depicts that, in some embodiments, circuitry 260 for analyzingthe received data for a time associated with the first medication eventincludes circuitry 1600. Circuitry 1600 includes: circuitry foridentifying a time component in the received data; circuitry forcomparing the identified time component with at least one time parameterassociated with an expected medication event for the individual; andcircuitry for determining, based on the comparisons, a time score forthe first medication event based on the received data. For example, insome embodiments, circuitry 1600 can include: circuitry for identifyinga clock time in the received data; circuitry for comparing theidentified clock time with at least one time range parameter associatedwith an expected medication event for the individual (i.e. the expectedtime range for the medication to be taken based on the medicationregimen); and circuitry for determining, based on the comparisons, atime score for the first medication event based on the received data. Atime score can include a range, or binary (e.g. yes/no) score. In someembodiments, the system includes circuitry for indicating the determinedtime score. For example, the determined time score can be indicated in atext, table, graph or color indicator (e.g. red light/green light)format. For example, the determined time score can be indicated on adevice utilized by at least one system user, (e.g. illustrated as 140and 145 in FIG. 1).

FIG. 17 shows aspects of the system 200 illustrated in FIG. 2. FIG. 17depicts that, in some embodiments, circuitry 260 for analyzing thereceived data for a time associated with the first medication eventincludes circuitry 1700. Circuitry 1700 includes: circuitry foridentifying a time component in the received data; circuitry forassociating the identifier of a first medication event for an individualwith an expected medication time for the individual; circuitry forcomparing the identified time component with the expected medicationtime; circuitry for determining, based on the comparison, a medicationevent time compliance score for the first medication event; andcircuitry for indicating the determined medication event time compliancescore for the first medication event. For example, circuitry 1700 caninclude: circuitry for identifying an elapsed time since the lastmedication event in the received data; circuitry for associating theidentifier of a first medication event for an individual with anexpected medication time for the individual; circuitry for comparing theidentified elapsed time since the last medication event with theexpected medication time; circuitry for determining, based on thecomparison, a medication event time compliance score for the firstmedication event; and circuitry for indicating the determined medicationevent time compliance score for the first medication event. In someembodiments, the system includes circuitry for indicating the determinedmedication event time compliance score. For example, the determinedmedication event time compliance score can be indicated in a text,table, graph or color indicator (e.g. red light/yellow light/greenlight) format. For example, the determined medication event timecompliance score can be indicated on a device utilized by at least onesystem user, (e.g. illustrated as 140 and 145 in FIG. 1).

FIG. 18 illustrates aspects of the system 200 shown in FIG. 2. FIG. 18illustrates that, in some embodiments, circuitry 270 for determining acompliance likelihood for the first medication event based on theanalyses of the received data includes circuitry 1800 and/or circuitry1810. Circuitry 1800 includes: circuitry for comparing the analyses witha set of parameters for a standard medication event; and circuitry forcalculating, based on the comparison, a compliance likelihood for thefirst medication event. For example, in some embodiments circuitry 1800includes circuitry for comparing one or more of the analyses with a setof parameters for a standard medication event; and circuitry forcalculating, based on the comparison, a compliance likelihood for thefirst medication event. For example in some embodiments circuitry 1800includes circuitry for comparing one or more of: the analysis of thereceived data for at least one attribute of an individual; the analysisof received data for at least one attribute relating to a medicationduring the first medication event; the analysis of the received data forat least one feature of visual information relating to the individualduring the first medication event; the analysis of the received data forat least one feature of non-visual information relating to theindividual during the first medication event; and the analysis of thereceived data for a time associated with the first medication event; andcircuitry for calculating, based on the comparison, a compliancelikelihood for the first medication event. Circuitry for calculating,based on the comparison, a compliance likelihood for the firstmedication event can include, for example, calculations based on theanalysis results, underlying data or input parameters. Circuitry 1810includes: circuitry for comparing the analyses with a set of parametersfor an expected medication event for the individual; and circuitry forcalculating, based on the comparison, a compliance likelihood for theindividual with the expected medication event. For example, circuitry1810 can include circuitry for comparing the analyses with a set ofparameters for an expected medication event for the individual, such astime parameters, audio aspect parameters, or visual feature parameters.

FIG. 19 shows aspects of the system 200 illustrated in FIG. 2. FIG. 19shows that, in some embodiments, the system 200 can include one or moreof circuitry 1900, 1910, 1920. Circuitry 1900 includes circuitry forsaving the determined compliance likelihood for the first medicationevent into a memory. For example, the saving the determined compliancelikelihood for the first medication event can include saving into a RAMmemory. For example, the saving the determined compliance likelihood forthe first medication event can include saving into memory in a computerhard drive or removable memory device. Circuitry 1910 includes circuitryfor saving the determined compliance likelihood for the first medicationevent into a health record for the individual. For example, thedetermined compliance likelihood can be saved into an existing healthrecord for the individual, or saved into a newly generated health recordfor the individual. Circuitry 1920 includes circuitry for comparing thedetermined compliance likelihood for the first medication event to acompliance goal for the individual; and circuitry for indicating thecomparison. For example, the comparison may communicate to a caregiveror the individual that there has been full compliance, or a lack ofcompliance.

FIG. 20 illustrates aspects of the system 200 shown in FIG. 2. FIG. 20depicts that, in some embodiments, the system 200 can include one ormore of circuitry 2000, 2010, 2020, 2030. Circuitry 2000 includes:circuitry for comparing the determined compliance likelihood for thefirst medication event to a determined compliance likelihood for asecond medication event for the individual; circuitry for comparing thedetermined compliance likelihood for the first medication event and thedetermined compliance likelihood for the second medication event to acompliance goal for the individual; and circuitry for indicating thecomparison. Circuitry 2010 includes: circuitry for receiving data. Forexample, the circuitry 2010 can be configured to receive data from amonitoring device (e.g. as 110 in FIG. 1). For example, the circuitry2010 can be configured to receive data processed from a signal (e.g. as115 in FIG. 1). Circuitry 2020 includes: circuitry for saving receiveddata into a memory. For example, the circuitry 2020 can be configured tosave data received from a monitoring device (e.g. as 110 in FIG. 1) intomemory in a hard drive. For example, the circuitry 2020 can beconfigured to save data received from a monitoring device (e.g. as 110in FIG. 1) into memory in a data storage device. Circuitry 2030includes: circuitry for saving the analyses of the received data into amemory. For example, circuitry 2030 can include saving at least one of:the analysis of the received data for at least one attribute of anindividual; the analysis of received data for at least one attributerelating to a medication during the first medication event; the analysisof the received data for at least one feature of visual informationrelating to the individual during the first medication event; theanalysis of the received data for at least one feature of non-visualinformation relating to the individual during the first medicationevent; and the analysis of the received data for a time associated withthe first medication event.

FIG. 21 shows aspects of the system 200 shown in FIG. 2. FIG. 21illustrates that, in some embodiments, the system 200 can include one ormore of circuitry 2100, 2110, 2120, 2130. Circuitry 2100 includes:circuitry for saving the analysis of the received data for an identifierof a first medication event for an individual into a memory. Circuitry2110 includes: circuitry for saving the analysis of the received datafor at least one attribute of an individual into a memory. Circuitry2120 includes: circuitry for saving the analysis of the received datafor at least one attribute relating to a medication during the firstmedication event into a memory. Circuitry 2130 includes: circuitry forsaving the analysis of the received data for at least one feature ofvisual information relating to the individual during the firstmedication event into a memory.

FIG. 22 shows aspects of a system such as illustrated in FIG. 2. FIG. 22depicts that, in some embodiments, the system 200 can include one ormore of circuitry 2200, 2210, 2220. In some embodiments, FIG. 22 depictsthat circuitry 2220 can include circuitry 2130. Circuitry 2200 includes:circuitry for saving the analysis of the received data for at least onefeature of non-visual information relating to the individual during thefirst medication event into a memory. Circuitry 2210 includes: circuitryfor saving the analysis of the received data for a time associated withthe first medication event into a memory. Circuitry 2220 includes:circuitry for comparing the analyses with a set of standard analysisparameters for a standard medication event; circuitry for determining,based on the comparison, if the analyses are within the standardanalysis parameters for the standard medication event; and circuitry forindicating the determination. In some embodiments, circuitry 2220 caninclude circuitry 2230. Circuitry 2230 includes: circuitry for savingthe determination into a memory.

FIG. 23 shows aspects of the system as illustrated in FIG. 2. FIG. 23depicts that, in some embodiments, the system 200 can include circuitry2300, which can also include circuitry 2310. Although circuitry 210,220, 230, 240 250, 260, 270 and 280 are not illustrated in FIG. 23 forclarity of presentation, they should be considered to be present insystem 200. As shown in FIG. 23, circuitry 2300 includes: circuitry foranalyzing received data for an identifier of a second medication eventfor the individual; circuitry for analyzing received data for the atleast one attribute of the individual; circuitry for analyzing thereceived data for the at least one attribute relating to a medicationduring the second medication event; circuitry for analyzing the receiveddata for at least one feature of visual information relating to theindividual during the second medication event; circuitry for analyzingthe received data for at least one feature of non-visual informationrelating to the individual during the second medication event; circuitryfor analyzing the received data for a time associated with the secondmedication event; circuitry for determining the compliance likelihoodfor the second medication event based on the analyses of the receiveddata; and circuitry for indicating the determined compliance likelihoodfor the second medication event. Circuitry 2310 includes: circuitry forcomparing the determined compliance likelihood for the first medicationevent and the determined compliance likelihood for the second medicationevent; circuitry for determining a composite compliance likelihood forthe first and second medication events; circuitry for saving thecomposite compliance likelihood into a memory; and circuitry forindicating the composite compliance likelihood.

FIG. 24 illustrates aspects of a computer system 120 including at leastone main computing unit 125. Although a single main computing unit 125is illustrated in FIG. 24, in some embodiments there may be a pluralityof main computing units 125. A main computing unit 125 includescomputer-readable storage medium including executable instructions formonitoring medication events relating to an individual 2400. Thecomputer-readable storage medium including executable instructions formonitoring medication events relating to an individual 2400 includesinstructions 2410, 2420, 2430, 2440, 2450, 2460, 2470 and 2480.Instructions 2410 include instructions for analyzing received data foran identifier of a first medication event for an individual. Forexample, the instruction can include instructions for analyzing receiveddata for an identifier, such as a code identifier, of a first medicationevent for an individual. Instructions 2420 include instructions foranalyzing the received data for at least one attribute of an individual.For example, instructions 2420 can include instructions for analyzingthe received data for at least one visual feature of an individual, suchas facial features. Instructions 2430 include instructions for analyzingthe received data for at least one attribute relating to a medicationduring the first medication event. For example, instructions 2430 caninclude instructions for analyzing the received data for the color orshape of pills. For example, instructions 2430 can include instructionsfor analyzing the received data for the size and shape of an inhalerdevice. Instructions 2440 include instructions for analyzing thereceived data for at least one feature of visual information relating tothe individual during the first medication event. For example, theinstructions 2440 can include instructions for analyzing the receiveddata for visual information relating to the individual placingmedication in pill form into his or her mouth. Instructions 2450 includeinstructions for analyzing the received data for at least one feature ofnon-visual information relating to the individual during the firstmedication event. For example, the instructions 2450 can includeinstructions for analyzing the received data for audio informationrelating to the use of an inhaler by the individual. For example, theinstructions 2450 can include instructions for analyzing the receiveddata for audio information relating to the individual swallowingmedication. Instructions 2460 include instructions for analyzing thereceived data for a time associated with the first medication event. Forexample, instructions 2460 can include instructions for analyzing thereceived data for a clock time associated with the first medicationevent. Instructions 2470 include instructions for determining acompliance likelihood for the first medication event based on theanalyses of the received data. Instructions 2480 include instructionsfor indicating the determined compliance likelihood for the firstmedication event. For example, the instructions 2480 can includeinstructions to indicate the determined compliance likelihood for thefirst medication event on a display attached to the main computing unit125. For example, the instructions 2480 can include instructions toindicate the determined compliance likelihood for the first medicationevent on a display attached to a secondary computing unit that are partof a system 120 (e.g. secondary computing units 130, 135 as illustratedin FIG. 1).

In some embodiments, the instructions 2410 for analyzing received datafor an identifier of a first medication event for an individual caninclude instructions for analyzing received data encoded in atransmission originating from a cell phone. For example, an individualcan send a transmission from a cell phone or smart phone to the system.In some embodiments, the instructions 2410 for analyzing received datafor an identifier of a first medication event for an individual caninclude instructions for analyzing received data encoded in atransmission originating from a portable computing device. For example,an individual can send a transmission from a laptop, PDA, or tabletcomputing device to the system. In some embodiments, the instructions2410 for analyzing received data for an identifier of a first medicationevent for an individual can include instructions for analyzing receiveddata encoded in a transmission originating from a fixed position cameraunit. For example, the medication event can occur in a location withinrange of a fixed position camera unit, which is configured to transmitdata regarding the medication event to the system. In some embodiments,the instructions 2410 for analyzing received data for an identifier of afirst medication event for an individual can include instructions foranalyzing the received data for an identifier that includes a timevalue. For example, the instructions can include instructions foranalyzing the received data for a clock time value. In some embodiments,the instructions 2410 for analyzing received data for an identifier of afirst medication event for an individual can include instructions foranalyzing received data for an identifier that includes a code. Forexample, an individual can enter a code into a keyboard attached to amonitoring device and the code may be transmitted to the system. Forexample, a code may be automatically generated by the system to identifya specific medication event. In some embodiments, the instructions 2410for analyzing received data for an identifier of a first medicationevent for an individual can include instructions for analyzing thereceived data for an identifier that includes at least one visualinformation feature. For example, the instructions can includeinstructions for analyzing the received data for an identifier thatincludes visual information regarding the individual. For example, theinstructions can include instructions for analyzing the received datafor an identifier that includes visual information regarding themedication label. For example, the instructions can include instructionsfor analyzing the received data for an identifier that includes visualinformation regarding the individual as well as the medication label. Insome embodiments, the instructions 2410 for analyzing received data foran identifier of a first medication event for an individual can includeinstructions for analyzing the received data for an identifier thatincludes at least one non-visual information feature. For example, theinstructions can include instructions for analyzing the received datafor an identifier that includes audio information, such as the sound ofthe individual swallowing or the sound of the individual using aninhaler. For example, the instructions can include instructions foranalyzing the received data for an identifier that includes thermalinformation, such as skin temperature of the individual during themedication event. In some embodiments, the instructions 2410 foranalyzing received data for an identifier of a first medication eventfor an individual can include instructions for analyzing the receiveddata for a radio-frequency identification (RFID) code. For example, anindividual or a caregiver can use a monitoring device to receive a RFIDsignal from the medication packaging, which can then be part of a datatransmission from the monitoring device.

In some embodiments, instructions 2420 for analyzing the received datafor at least one attribute of an individual can include: instructionsfor associating the identifier of the first medication event with anexpected individual; instructions for retrieving one or more specificidentifiers associated with the expected individual; instructions foranalyzing the received data for the presence or absence of at least oneof the one or more specific identifiers; and instructions for indicatingthe presence or absence of the expected individual based on theanalysis. In some embodiments, instructions 2420 for analyzing thereceived data for at least one attribute of an individual can include:instructions for associating the identifier of the first medicationevent with an expected individual; instructions for retrieving one ormore attributes associated with the expected individual; instructionsfor comparing the retrieved one or more attributes associated with theexpected individual with the received data; instructions fordetermining, based on the comparison, a confirmation likelihood for theexpected individual; and instructions for indicating the determinedconfirmation likelihood for the expected individual. In someembodiments, instructions 2420 for analyzing the received data for atleast one attribute of an individual can include: instructions foranalyzing the received data for at least one attribute of theindividual; instructions for comparing the at least one attribute of theindividual with a set of attribute parameters for an expectedindividual; and instructions for determining, based on the comparison,an attribute score for the at least one attribute of the individual. Forexample, the instructions can include instructions for comparing atleast one facial feature of the individual with a set of facial featureparameters for an expected individual, such as a percentage of the faceincluded in the data, or eye color discernible from the data. Theinstructions can include instructions for presenting the attribute scorein a visual format, such as a table, text, or a graph. The instructionscan include instructions for saving the attribute score in a memory.

In some embodiments, instructions 2430 for analyzing the received datafor at least one attribute relating to a medication during the firstmedication event can include instructions for analyzing received datafor an attribute that includes at least one visual information feature.For example, the instructions can include instructions for analyzingreceived data for a visual feature of the medication, such as pillcolor, size, inhaler shape, medication label, or visual features of themedication packaging. In some embodiments, instructions 2430 foranalyzing the received data for at least one attribute relating to amedication during the first medication event can include instructionsfor analyzing received data for an attribute that includes at least onenon-visual information feature. For example, the instructions caninclude instructions for analyzing received data for an audio attributeof an inhaler, a thermal attribute of a syringe, or a micropower impulseradar (MIR) attribute of the medication. In some embodiments,instructions 2430 for analyzing the received data for at least oneattribute relating to a medication during the first medication event caninclude instructions for analyzing received data for an attribute thatincludes a radio-frequency identification (RFID) code. For example, amonitoring device can receive RFID signals from the packaging of amedication and transmit those signals to the system for analysis.

In some embodiments, instructions 2430 for analyzing the received datafor at least one attribute relating to a medication during the firstmedication event can include: instructions for analyzing the receiveddata for at least one attribute of the medication; instructions forcomparing the at least one attribute of the medication with a set ofattribute parameters for an expected medication; and instructions fordetermining, based on the comparison, an attribute score for the atleast one attribute of the medication. In some embodiments, instructions2430 for analyzing the received data for at least one attribute relatingto a medication during the first medication event can include:instructions for associating the identifier of the first medicationevent with an expected medication; instructions for retrieving one ormore specific identifiers associated with the expected medication;instructions for analyzing the received data for the presence or absenceof at least one of the one or more specific identifiers; andinstructions for indicating the presence or absence of the expectedmedication based on the analysis. For example, instructions 2430 caninclude: instructions for associating the identifier of the firstmedication event with an expected medication, such as an expectedmedication for a specific individual at that distinct medication event;instructions for retrieving one or more specific identifiers associatedwith the expected medication, such as visual aspects of the medicationpackaging; instructions for analyzing the received data for the presenceor absence of at least one of the one or more specific identifiers, suchas the visual aspects of the medication packaging; and instructions forindicating the presence or absence of the expected medication based onthe analysis. The indication can be carried out, for example, on a maincomputing unit (e.g. item 125 in FIG. 1), or a secondary computing unit(e.g. items 135, 140 in FIG. 1). Instructions for indicating thepresence or absence of the expected medication based on the analysis canalso be sent to a monitoring device (e.g. item 110 in FIG. 1), for theindividual patient or a caregiver at the site of the medication event toobtain a medication confirmation during the medication event. In someembodiments, instructions 2430 for analyzing the received data for atleast one attribute relating to a medication during the first medicationevent can include: instructions for associating the identifier of thefirst medication event with an expected medication; instructions forretrieving one or more attributes associated with the expectedmedication; instructions for comparing the retrieved one or moreattributes associated with the expected medication with the receiveddata; instructions for determining, based on the comparison, aconfirmation likelihood for the expected medication; and instructionsfor indicating the determined confirmation likelihood for the expectedmedication.

In some embodiments, instructions 2440 for analyzing the received datafor the at least one feature of visual information relating to theindividual during the first medication event can include: instructionsfor identifying a visual information component of the received data;instructions for comparing the identified visual information componentof the received data with at least one visual information parameter; andinstructions for determining a likelihood of sufficiency for the visualinformation component of the received data based on the comparison. Insome embodiments, instructions 2440 for analyzing the received data forthe at least one feature of visual information relating to theindividual during the first medication event can include: instructionsfor associating the identifier of the first medication event with a setof visual information parameters for a standard medication event;instructions for comparing the at least one feature of visualinformation relating to the individual during the first medication eventwith the set of visual information parameters for the standardmedication event; instructions for determining, based on the comparison,a medication event compliance score for the first medication event; andinstructions for indicating the determined medication event compliancescore for the first medication event.

In some embodiments, instructions 2450 for analyzing the received datafor the at least one feature of non-visual information relating to theindividual during the first medication event can include: instructionsfor analyzing the received data for the at least one feature ofnon-visual information including near-infrared (IR) information. In someembodiments, instructions 2450 for analyzing the received data for theat least one feature of non-visual information relating to theindividual during the first medication event can include: instructionsfor analyzing the received data for the at least one feature ofnon-visual information including auditory information. In someembodiments, instructions 2450 for analyzing the received data for theat least one feature of non-visual information relating to theindividual during the first medication event can include: instructionsfor analyzing the received data for the at least one feature ofnon-visual information including thermal information. In someembodiments, instructions 2450 for analyzing the received data for theat least one feature of non-visual information relating to theindividual during the first medication event can include: instructionsfor analyzing the received data for the at least one feature ofnon-visual information including kinetic information. In someembodiments, instructions 2450 for analyzing the received data for theat least one feature of non-visual information relating to theindividual during the first medication event can include: instructionsfor analyzing the received data for the at least one feature ofnon-visual information including micropower impulse radar (MIR)information.

In some embodiments, instructions 2450 for analyzing the received datafor the at least one feature of non-visual information relating to theindividual during the first medication event can include: instructionsfor identifying a non-visual information component of the received data;instructions for comparing the identified non-visual informationcomponent of the received data with at least one non-visual informationparameter; and instructions for determining a likelihood of sufficiencyfor the non-visual information component of the received data based onthe comparison. In some embodiments, instructions 2450 for analyzing thereceived data for the at least one feature of non-visual informationrelating to the individual during the first medication event caninclude: instructions for associating the identifier of the firstmedication event with a set of non-visual information parameters for astandard medication event; instructions for comparing the at least onefeature of non-visual information relating to the individual during thefirst medication event with the set of non-visual information parametersfor the standard medication event; instructions for determining, basedon the comparison, a medication event compliance score for the firstmedication event; and instructions for indicating the determinedmedication event compliance score for the first medication event.

In some embodiments, instructions 2460 for analyzing the received datafor a time associated with the first medication event includes:instructions for identifying a time component in the received data;instructions for comparing the identified time component with at leastone time parameter associated with an expected medication event for theindividual; and instructions for determining, based on the comparisons,a time score for the first medication event based on the received data.In some embodiments, instructions 2460 for analyzing the received datafor a time associated with the first medication event includes:instructions for identifying a time component in the received data;instructions for associating the identifier of a first medication eventfor an individual with an expected medication time for the individual;instructions for comparing the identified time component with theexpected medication time; instructions for determining, based on thecomparison, a medication event time compliance score for the firstmedication event; and instructions for indicating the determinedmedication event time compliance score for the first medication event.

In some embodiments, instructions 2470 for determining the compliancelikelihood for the first medication event based on the analyses of thereceived data includes: instructions for comparing the analyses with aset of parameters for a standard medication event; and instructions forcalculating, based on the comparison, a compliance likelihood for thefirst medication event. In some embodiments, instructions 2470 fordetermining the compliance likelihood for the first medication eventbased on the analyses of the received data includes: instructions forcomparing the analyses with a set of parameters for an expectedmedication event for the individual; and instructions for calculating,based on the comparison, a compliance likelihood for the individual withthe expected medication event.

As illustrated in FIG. 24, main computing unit 125 includescomputer-readable storage medium including executable instructions formonitoring medication events relating to an individual 2400. Thecomputer-readable storage medium including executable instructions formonitoring medication events relating to an individual 2400 includesinstructions 2410, 2420, 22430, 2440, 2450, 2460 and 2470. In someembodiments, the computer-readable storage medium including executableinstructions for monitoring medication events relating to an individual2400 includes additional instructions. In some embodiments, thecomputer-readable storage medium including executable instructions formonitoring medication events relating to an individual 2400 includesinstructions for saving the determined compliance likelihood for thefirst medication event into memory. For example, the instructions caninclude instructions for saving the determined compliance likelihood forthe first medication event into computer memory, such as a hard drive inthe main computing unit 125. In some embodiments, the computer-readablestorage medium including executable instructions for monitoringmedication events relating to an individual 2400 includes instructionsfor saving the determined compliance likelihood for the first medicationevent into a health record for the individual. For example, theinstructions can include instructions for saving the determinedcompliance likelihood into a health record for the individual intocomputer memory, such as in the main computing unit 125. In someembodiments, the computer-readable storage medium including executableinstructions for monitoring medication events relating to an individual2400 includes instructions for comparing the determined compliancelikelihood for the first medication event to a compliance goal for theindividual; and instructions for indicating the comparison. For example,the instructions can include instructions for indicating the comparisonon a display device attached to the main computing unit 125.

In some embodiments, the computer-readable storage medium includingexecutable instructions for monitoring medication events relating to anindividual 2400 includes instructions for instructions for comparing thedetermined compliance likelihood for the first medication event to adetermined compliance likelihood for a second medication event for theindividual; instructions for comparing the determined compliancelikelihood for the first medication event and the determined compliancelikelihood for the second medication event to a compliance goal for theindividual; and instructions for indicating the comparison. For example,the instructions can include instructions for indicating the comparisonon a display device attached to the main computing unit 125. In someembodiments, the computer-readable storage medium including executableinstructions for monitoring medication events relating to an individual2400 includes instructions for receiving data. For example, theinstructions for receiving data can include instructions for receivingdata from a monitoring device (e.g. item 110 in FIG. 1).

In some embodiments, the computer-readable storage medium includingexecutable instructions for monitoring medication events relating to anindividual 2400 includes instructions for saving received data into amemory. For example, the instructions for saving received data into amemory can include saving received data into computer memory, such as inthe main computing unit 125. In some embodiments, the computer-readablestorage medium including executable instructions for monitoringmedication events relating to an individual 2400 includes instructionsfor saving the analyses of the received data into a memory. In someembodiments, the computer-readable storage medium including executableinstructions for monitoring medication events relating to an individual2400 includes instructions for saving the analysis of the received datafor at least one attribute of an individual into a memory. In someembodiments, the computer-readable storage medium including executableinstructions for monitoring medication events relating to an individual2400 includes instructions for saving the analysis of the received datafor at least one attribute relating to a medication during the firstmedication event into a memory. In some embodiments, thecomputer-readable storage medium including executable instructions formonitoring medication events relating to an individual 2400 includesinstructions for saving the analysis of the received data for at leastone feature of visual information relating to the individual during thefirst medication event into a memory. In some embodiments, thecomputer-readable storage medium including executable instructions formonitoring medication events relating to an individual 2400 includesinstructions for saving the analysis of the received data for at leastone feature of non-visual information relating to the individual duringthe first medication event into a memory. In some embodiments, thecomputer-readable storage medium including executable instructions formonitoring medication events relating to an individual 2400 includesinstructions for saving the analysis of the received data for a timeassociated with the first medication event into a memory. For example,the instructions for saving one or more of the analyses into a memorycan include saving into computer memory, such as in the main computingunit 125.

In some embodiments, the computer-readable storage medium includingexecutable instructions for monitoring medication events relating to anindividual 2400 includes instructions for comparing the analyses with aset of standard analysis parameters for a standard medication event;instructions for determining, based on the comparison, if the analysesare within the standard analysis parameters for the standard medicationevent; and instructions for indicating the determination. In someembodiments, the instructions for determining, based on the comparison,if the analyses are within the standard analysis parameters for thestandard medication event includes instructions for saving thedetermination into a memory. For example, the instructions for savingthe determination into a memory can include saving into computer memory,such as in the main computing unit 125. In some embodiments, thecomputer-readable storage medium including executable instructions formonitoring medication events relating to an individual 2400 includesinstructions for analyzing the received data for an identifier of asecond medication event for the individual; instructions for analyzingthe received data for the at least one attribute of the individual;instructions for analyzing the received data for the at least oneattribute relating to a medication during the second medication event;instructions for analyzing the received data for at least one feature ofvisual information relating to the individual during the secondmedication event; instructions for analyzing the received data for atleast one feature of non-visual information relating to the individualduring the second medication event; instructions for analyzing thereceived data for a time associated with the second medication event;instructions for determining a compliance likelihood for the secondmedication event based on the analyses of the received data; andinstructions for indicating the determined compliance likelihood for thesecond medication event. In some embodiments, the computer-readablestorage medium including executable instructions for monitoringmedication events relating to an individual 2400 includes instructionsfor comparing the determined compliance likelihood for the firstmedication event and the determined compliance likelihood for the secondmedication event; instructions for determining a composite compliancelikelihood for the first and second medication events; instructions forsaving the composite compliance likelihood into a memory; andinstructions for indicating the composite compliance likelihood.

FIG. 25 illustrates a flowchart of a method 2500 for monitoringmedication events relating to an individual. These method steps can becarried out, for example, by a computer system (e.g. item 120 in FIG.1). FIG. 25 shows that the method includes a series of steps, 2510,2520, 2530, 2540, 2550, 2560, 2570, 2580. Method step 2510 includesanalyzing received data for an identifier of a first medication eventfor an individual, the received data originating from at least onemonitoring device (e.g. item 110 in FIG. 1). Method step 2520 includesanalyzing the received data for at least one attribute of an individual.For example, analyzing the received data for at least one attribute ofan individual can include analyzing the received data for a codeassociated with a particular individual. Method step 2530 includesanalyzing the received data for at least one attribute relating to amedication during the first medication event. For example, the methodcan include analyzing the received data for at least one visualattribute relating to a medication during the first medication event,such as the color and design of the medication packaging. Method step2540 includes analyzing the received data for at least one feature ofvisual information relating to the individual during the firstmedication event. For example, the method can include analyzing thereceived data for at least one feature of visual information relating tothe individual that includes a visual feature, such as facial featuresof the individual. Method step 2550 includes analyzing the received datafor at least one feature of non-visual information relating to theindividual during the first medication event. For example, the methodcan include analyzing the received data for at least one feature ofnon-visual information relating to the individual that includes an audiofeature, such as from a recording of the individual stating “I am takingmy medication now.” Method step 2560 includes analyzing the receiveddata for a time associated with the first medication event. For example,the method can include analyzing the received data for a clock timeassociated with the first medication event, such as “between 2:00 PM and2:30 PM.” Method step 2570 includes determining a compliance likelihoodfor the first medication event based on the analyses of the receiveddata. Method step 2580 includes indicating the determined compliancelikelihood for the first medication event. For example, the determinedcompliance likelihood for the first medication event can be displayed ona monitor attached to the computer system (e.g. item 120 in FIG. 1).Other aspects of the method steps can be identified in the text andclaims herein.

FIG. 26 illustrates a system 2600 for monitoring medication events. Thesystem 2600 can, for example, be part of a computer system (see item 120in FIG. 1). The system 2600 includes circuitry 2610, 2620, 2630, 2640,2650, 2660, 2670, 2680, 2690, 2695. The circuitry is configured to carryout specific processes. Circuitry 2610 includes circuitry for acceptingdata regarding a medication event for an individual. Circuitry 2620includes circuitry for extracting, from the accepted data regarding themedication event for the individual, one or more identifiers of themedication. Circuitry 2630 includes circuitry for comparing the one ormore identifiers of the medication with a set of standard medicationidentifier parameters. Circuitry 2640 includes circuitry for extracting,from the accepted data regarding the medication event for theindividual, one or more visual features of the medication event.Circuitry 2650 includes circuitry for comparing the one or more visualfeatures of the medication event with a set of medication eventparameters. Circuitry 2660 includes circuitry for extracting, from theaccepted data regarding the medication event for the individual, one ormore non-visual features of the medication event. Circuitry 2670includes circuitry for comparing the one or more non-visual features ofthe medication event with the set of medication event parameters.Circuitry 2680 includes circuitry for extracting, from the accepted dataregarding the medication event for the individual, a time associatedwith the medication event. Circuitry 2690 includes circuitry forcomparing the time associated with the medication event with an expectedmedication event time for the individual. Circuitry 2695 includescircuitry for saving the comparisons into a memory. For example, thecircuitry 2695 can include circuitry for saving the comparisons into acomputer system memory, (such as part of item 120 in FIG. 1).

FIG. 27 illustrates aspects of the system 2600 for monitoring medicationevents shown in FIG. 26. FIG. 27 depicts that, in some embodiments,circuitry 2610 for accepting data regarding a medication event for anindividual can include one or more of circuitry 2700, 2710, 2720, 2730and 2740. Circuitry 2610 for accepting data regarding a medication eventfor an individual can include circuitry 2700 for accepting dataoriginating from a cell phone. For example, a cell phone including acamera and microphone can be used as a monitoring device in a medicationevent (see, e.g. item 110 in FIG. 1). Circuitry 2610 for accepting dataregarding a medication event for an individual can include circuitry2710 for accepting data originating from a portable computing device.For example, a portable computing device, such as a laptop, PDA ortablet, including a camera and microphone can be used as a monitoringdevice in a medication event (see, e.g. item 110 in FIG. 1). Circuitry2610 for accepting data regarding a medication event for an individualcan include circuitry 2720 for accepting data originating from a fixedposition camera unit. For example, a fixed position camera unit, such asa camera unit configured to be affixed to a wall, and including amicrophone, can be used as a monitoring device in a medication event(see, e.g. item 110 in FIG. 1). Circuitry 2610 for accepting dataregarding a medication event for an individual can include circuitry2730 for accepting data originating from a plurality of devices. Forexample, a plurality of devices, such as more than one fixed positioncamera unit, such as a camera unit configured to be affixed to a wall,and each including microphones, can be used as a plurality of monitoringdevices for a medication event (see, e.g. item 110 in FIG. 1). Circuitry2610 for accepting data regarding a medication event for an individualcan include circuitry 2740 for accepting data originating from amicropower impulse radar (MIR) device. For example, a micropower impulseradar (MIR) device, can be used with a camera as monitoring devices fora medication event (see, e.g. item 110 in FIG. 1).

FIG. 28 shows aspects of the system 2600 for monitoring medicationevents shown in FIG. 26. FIG. 28 illustrates that, in some embodiments,circuitry 2620 for extracting, from the accepted data regarding themedication event for the individual, one or more identifiers of themedication, includes one or more of circuitry 2800, 2810. Circuitry 2620for extracting, from the accepted data regarding the medication eventfor the individual, one or more visual features of the medication caninclude circuitry 2800 for extracting visual data. For example,circuitry 2800 for extracting visual data can include extracting dataoriginating from a camera device. Circuitry 2620 for extracting, fromthe accepted data regarding the medication event for the individual, oneor more visual features of the medication can include circuitry 2810 forextracting radio frequency identification (RFID) information. Forexample, circuitry 2810 for extracting radio frequency identification(RFID) information can include extracting data originating from areflected RFID signal, such as a RFID signal reflected from themedication label.

FIG. 28 depicts aspects of the system 2600 for monitoring medicationevents shown in FIG. 26. FIG. 28 shows that, in some embodiments,circuitry 2630 for comparing the one or more identifiers of themedication with a set of standard medication identifier parameters,includes circuitry 2820. Circuitry 2630 for comparing the one or moreidentifiers of the medication with a set of standard medicationidentifier parameters can include circuitry 2820 for comparing visualfeatures. For example, circuitry 2820 for comparing visual features ofthe medication, such as size, shape and color of pills. For example,circuitry 2820 for comparing visual features of the medication, such assize, shape and color of a medication dispenser (e.g. a syringe unit oran inhaler unit).

FIG. 28 shows aspects of the system 2600 for monitoring medicationevents shown in FIG. 26. FIG. 28 illustrates that, in some embodiments,circuitry 2640 for extracting, from the accepted data regarding themedication event for the individual, one or more visual features of themedication event, includes circuitry 2830 for extracting one or morevisual features over time. For example, circuitry 2830 for extractingone or more visual features over time can include extracting one or morevisual features over time from a series of camera images taken by thesame camera device during the medication event. For example, circuitry2830 for extracting one or more visual features over time can includeextracting one or more visual features over time from a video taken by asingle camera device during the medication event. For example, circuitry2830 for extracting one or more visual features over time can includeextracting one or more visual features over time from a series of cameraimages taken by multiple camera units over time during the medicationevent.

FIG. 29 shows aspects of the system 2600 for monitoring medicationevents shown in FIG. 26. FIG. 29 illustrates that, in some embodiments,circuitry 2650 for comparing the one or more visual features of themedication event with a set of medication event parameters includescircuitry 2900. Circuitry 2900 includes circuitry for determining, froma set of standard medication event visual features, at least oneexpected visual feature; and circuitry for comparing the accepted dataregarding the medication event for the individual with the determined atleast one expected visual feature. For example, the system can utilize alook-up table to obtain a set of standard medication event visualfeatures. The system can then determine, from the set, which of thestandard medication event visual features are relevant to a particularmedication. A system can determine, for example, that the position of aninhaler relative to the individual's mouth during use is a standardmedication event visual features for a particular medication that isadministered with an inhaler device. The system can then comparing theaccepted data regarding the medication event for the individual with thedetermined at least one expected visual feature, such as the position ofthe specific inhaler device relative to the individual's mouth.

FIG. 29 illustrates aspects of the system 2600 for monitoring medicationevents shown in FIG. 26. FIG. 29 illustrates that, in some embodiments,circuitry 2660 for extracting, from the accepted data regarding themedication event for the individual, one or more non-visual features ofthe medication event, includes circuitry 2910. Circuitry 2910 includescircuitry for extracting the one or more non-visual features over time.For example, the system can utilize a look-up table to obtain a set ofstandard medication event visual features. The system can thendetermine, from the set, which of the standard medication eventnon-visual features are relevant to a particular medication. A systemcan determine, for example, that the sound of an inhaler during use is astandard medication event visual features for a particular medicationthat is administered with an inhaler device. The system can thencomparing the accepted data regarding the medication event for theindividual with the determined at least one expected non-visual feature,such as the sound generated by a specific inhaler device during use.

FIG. 30 shows aspects of the system 2600 for monitoring medicationevents shown in FIG. 26. FIG. 30 depicts that, in some embodiments,circuitry 2660 for extracting, from the accepted data regarding themedication event for the individual, one or more non-visual features ofthe medication event, includes one or more of circuitry 3000, 3010,3020, 3030. In some embodiments, circuitry 2660 for extracting, from theaccepted data regarding the medication event for the individual, one ormore non-visual features of the medication event, includes circuitry3000 for extracting one or more audio features. For example, circuitry3000 for extracting one or more audio features can include extractingone or more audio features from the use of a medication, such as aninhaler device, during the medication event. For example, circuitry 3000for extracting one or more audio features can include extracting one ormore audio features from the opening of a medication package, such as aparticular sound of a package being broken open, during the medicationevent. For example, circuitry 3000 for extracting one or more audiofeatures can include extracting one or more audio features generated bythe individual or a caregiver, such as the individual saying “I amtaking my medication now.” In some embodiments, circuitry 2660 forextracting, from the accepted data regarding the medication event forthe individual, one or more non-visual features of the medication event,includes circuitry 3010 for extracting one or more near-infrared (IR)features. For example, circuitry 3010 for extracting one or morenear-infrared (IR) features can include extracting one or more near-IRfeatures from the data obtained during the medication event, such as thenear-IR conditions of a medication device. For example, circuitry 3010for extracting one or more near-infrared (IR) features can includeextracting one or more near-IR features from the data obtained duringthe medication event, such as the near-IR conditions of an individual'sthroat while drinking during a medication event. For example, circuitry3010 for extracting one or more near-infrared (IR) features can includeextracting one or more near-IR features from the data obtained duringthe medication event, such as the near-IR conditions of an individual'sskin adjacent to an injection site during a medication event. In someembodiments, circuitry 2660 for extracting, from the accepted dataregarding the medication event for the individual, one or morenon-visual features of the medication event, includes circuitry 3020 forextracting one or more thermal features. For example, circuitry 3020 forextracting one or more thermal features can include extracting one ormore thermal features of a medication administration device during themedication event. A change in thermal features can indicate that amedication administration device, such as an inhaler, has been utilizedcorrectly during the medication event. For example, circuitry 3020 forextracting one or more thermal features can include extracting one ormore thermal features of an individual's skin during the medicationevent. A change in thermal features of an individual's skin during themedication event can indicate, for example, that a medication injectedvia syringe has been properly administered. In some embodiments,circuitry 2660 for extracting, from the accepted data regarding themedication event for the individual, one or more non-visual features ofthe medication event, includes circuitry 3030 for extracting one or morefeatures detectable by micropower impulse radar (MIR). For example,circuitry 3030 for extracting one or more features detectable bymicropower impulse radar (MIR) can include extracting one or morefeatures of an individual's physiology, such as respiration rate orheart rate. See: “Micropower Impulse Radar,” Azevedo and McEwan, Scienceand Technology Review, January/February 1996, pages 17-29; and US PatentApplication Publications No. 2004/0249257 and 2004/0249258 to Tupin etal., each titled “Article of Manufacture for Extracting PhysiologicalData Using Ultra-Wideband Radar and Improved Signal ProcessingTechniques,” which are all incorporated by reference herein. See also:US Patent Application Publication No. 2009/0227882 to Foo, titled “UltraWideband Monitoring Systems and Antennas,” which is incorporated byreference herein.

FIG. 31 illustrates aspects of the system 2600 for monitoring medicationevents shown in FIG. 26. FIG. 31 shows that, in some embodiments,circuitry 2670 for comparing the one or more non-visual features of themedication event with the set of medication event parameters includescircuitry 3100. In some embodiments, circuitry 2670 includes circuitry3100 for determining, from the set of standard medication eventnon-visual parameters, expected parameters for at least one expectednon-visual feature; and circuitry for comparing the accepted dataregarding the medication event for the individual with the expectedparameters for at least one expected non-visual feature. For example,circuitry 3100 can include determining, from the set of standardmedication event audio parameters, expected parameters for at least oneexpected audio feature, such as the sound of an inhaler deviceadministering a medication to an individual; and circuitry for comparingthe accepted data regarding the medication event for the individual withthe expected parameters for at least one expected audio feature. Forexample, circuitry 3100 can include determining, from the set ofstandard medication event audio parameters, expected parameters for atleast one expected thermal feature, such as the skin temperature of anindividual at a site adjacent to an injection during the injection; andcircuitry for comparing the accepted data regarding the medication eventfor the individual with the expected parameters for at least oneexpected thermal feature.

FIG. 32 shows aspects of the system 2600 for monitoring medicationevents shown in FIG. 26. FIG. 32 illustrates that, in some embodiments,circuitry 2680 for extracting, from the accepted data regarding themedication event for the individual, a time associated with themedication event includes one or more of circuitry 3200, 3210. Circuitry3200 includes circuitry for extracting a clock time associated with themedication event. For example, circuitry 3200 can include extracting aclock time associated with the medication event, such as “the nextmedication event is scheduled for 1:00 PM.” Circuitry 3210 includescircuitry for extracting a time interval associated with the medicationevent. For example, circuitry 3210 can include extracting a timeinterval associated with the medication event that is a range, such as“the next medication event is scheduled for between 8:30 AM and 9:00AM.” For example, circuitry 3210 can include extracting a time intervalassociated with the medication event that is an interval from anotherevent, such as a prior medication event for a meal. For example,circuitry 3210 can include extracting a time interval associated withthe medication event such as “the next medication event is due no morethan 1 hour after the completion of the individual's breakfast.”

FIG. 33 depicts aspects of the system 2600 for monitoring medicationevents shown in FIG. 26. FIG. 33 shows that, in some embodiments,circuitry 2690 for comparing the time associated with the medicationevent with the expected medication event time for the individualincludes circuitry 3300. Circuitry 3300 includes: circuitry fordetermining, from a set of standard medication event times, at least oneexpected medication event time; and circuitry for comparing theextracted time associated with the medication event with the determinedat least one expected medication event time.

FIG. 33 shows aspects of the system 2600 for monitoring medicationevents shown in FIG. 26. FIG. 33 illustrates that, in some embodiments,the system includes circuitry 3310. Circuitry 3310 includes circuitryfor determining, from the comparison of the one or more identifiers ofthe medication with the set of standard medication identifierparameters, if the one or more identifiers of the medication are withinthe set of standard medication identifier parameters. For example, a setof standard medication identifier parameters can include a number ofpills, and the system can compare the number of pills detected in thereceived data with the extected number to determine if the correctnumber of pills were detected. For example, a set of standard medicationidentifier parameters can include the color and shape of the medicationpackaging, and the system can compare and determine if the standardpackaging was detected. In some embodiments, the determination if theone or more identifiers of the medication are within the set of standardmedication identifier parameters can be indicated to a caregiver, suchas through a display device attached to the computer system (e.g. item120 in FIG. 1). In some embodiments, the determination if the one ormore identifiers of the medication are within the set of standardmedication identifier parameters can be indicated to the individual,such as through a display device attached to the monitoring device (e.g.item 110 in FIG. 1).

FIG. 34 depicts aspects of the system 2600 for monitoring medicationevents shown in FIG. 26. FIG. 34 shows that, in some embodiments, thesystem includes one or more of circuitry 3400, 3410. Circuitry 3400includes circuitry for determining, from the comparison of the one ormore non-visual features of the medication event with the set ofmedication event parameters, if the one or more non-visual features ofthe medication event are within the set of medication event parameters.Circuitry 3410 includes circuitry for determining, from the comparisonof the time associated with the medication event with the expectedmedication event time for the individual, if the time associated withthe medication event is within the expected medication event time forthe individual.

FIG. 35 illustrates aspects of the system 2600 for monitoring medicationevents shown in FIG. 26. FIG. 35 depicts that, in some embodiments, thesystem includes one or more of circuitry 3500, 3510, 3520, 3530.Circuitry 3500 includes circuitry for saving one or more of thecomparisons into a medical record for the individual. For example, amedical record can be saved into computer memory in the computer system(e.g. item 120 in FIG. 1). Circuitry 3510 includes circuitry fordetermining, from the comparisons, a medication compliance score for themedication event. In some embodiments, the a medication compliance scorefor the medication event can be saved into computer memory. In someembodiments, the a medication compliance score for the medication eventcan be indicated to a caregiver or the individual, such as through adisplay device attached to the computer system (e.g. item 120 in FIG. 1)or integrated in a monitoring device (e.g. item 110 in FIG. 1).Circuitry 3520 includes circuitry for indicating one or more of thecomparisons. For example, the comparisons can be indicated to acaregiver or the individual, such as through a display device attachedto the computer system (e.g. item 120 in FIG. 1) or integrated in amonitoring device (e.g. item 110 in FIG. 1). Circuitry 3530 includescircuitry for activating, depending on one or more of the comparisons,an alert indicator. For example, an alert indicator within the computersystem (e.g. item 120 in FIG. 1) can be activated to notify caregiversto review the medication event.

FIG. 36 shows aspects of the system 2600 for monitoring medicationevents shown in FIG. 26. FIG. 36 illustrates that, in some embodiments,the system includes circuitry 3600, which can include circuitry 3610.Circuitry 3600 includes: circuitry for accepting data regarding a secondmedication event for the individual; circuitry for extracting, from theaccepted data regarding the second medication event for the individual,one or more identifiers of the medication; circuitry for comparing theone or more identifiers of the medication with a set of standardmedication identifier parameters; circuitry for extracting, from theaccepted data regarding the second medication event for the individual,one or more visual features of the medication event; circuitry forcomparing the one or more visual features of the second medication eventwith a set of medication event parameters; circuitry for extracting,from the accepted data regarding the second medication event for theindividual, one or more non-visual features of the second medicationevent; circuitry for comparing the one or more non-visual features ofthe second medication event with the set of medication event parameters;circuitry for extracting, from the accepted data regarding the secondmedication event for the individual, a time associated with the secondmedication event; circuitry for comparing the time associated with thesecond medication event with an expected second medication event timefor the individual; and circuitry for saving the comparisons associatedwith the second medication event into a memory. Circuitry 3600 caninclude circuitry 3610, which includes: circuitry for determining, fromthe saved comparisons associated with the medication event and thecomparisons associated with the second medication event, if themedication events meet at least one standard; and circuitry foractivating an indicator in response to the determination.

FIG. 37 shows aspects of a computer system 120 including at least onemain computing unit 125. Although a single main computing unit 125 isillustrated in FIG. 37, in some embodiments there may be a plurality ofmain computing units 125. A main computing unit 125 includescomputer-readable storage medium including executable instructions formonitoring medication events relating to an individual 3700. Thecomputer-readable storage medium including executable instructions formonitoring medication events relating to an individual 3700 includesinstructions 3710, 3720, 3730, 3740, 3750, 3760, 3770, 3780, 3790 and3795. Instructions 3710 include instructions for accepting dataregarding a medication event for an individual. For example, theinstructions 3710 can include instructions for accepting data regardinga medication event for an individual from a monitoring device (e.g. item110 in FIG. 1). Instructions 3720 include instructions for extracting,from the accepted data regarding the medication event for theindividual, one or more identifiers of the medication. For example, theinstructions 3720 can include instructions for extracting, from theaccepted data regarding the medication event for the individual, one ormore identifiers of the medication such as color, shape and size ofpills for a medication in pill form. For example, the instructions 3720can include instructions for extracting, from the accepted dataregarding the medication event for the individual, one or moreidentifiers of the medication such as visual aspects of a medicationdevice, such as an inhaler or a syringe. For example, the instructions3720 can include instructions for extracting, from the accepted dataregarding the medication event for the individual, one or moreidentifiers of the medication such as non-visual identifiers such as aRFID code extracted from a reflection from a RFID tag on the medicationor medication packaging. Instructions 3730 include instructions forcomparing the one or more identifiers of the medication with a set ofstandard medication identifier parameters. For example, a RFID codeextracted from a reflection from a RFID tag on the medication ormedication packaging can be compared to a set of standard RFID codesfrom medications or medication packaging. Instructions 3740 includeinstructions for extracting, from the accepted data regarding themedication event for the individual, one or more visual features of themedication event. For example, instructions 3740 can includeinstructions for extracting, from the accepted data regarding themedication event for the individual, one or more visual features of themedication event from data obtained by a camera unit integrated within amonitoring device (e.g. item 110 in FIG. 1). Instructions 3750 includeinstructions for comparing the one or more visual features of themedication event with a set of medication event parameters. For example,facial image data from the individual can be compared with a set ofvisible medication event parameters. Instructions 3760 includeinstructions for extracting, from the accepted data regarding themedication event for the individual, one or more non-visual features ofthe medication event. For example, instructions 3760 can includeinstructions for extracting, from the accepted data regarding themedication event for the individual, one or more audio features of themedication event from data obtained by a microphone integrated within amonitoring device (e.g. item 110 in FIG. 1). Instructions 3770 includeinstructions for comparing the one or more non-visual features of themedication event with the set of medication event parameters. Forexample, instructions 3770 can include instructions for comparing theaudio features of the medication event with the set of medication eventparameters, such as the audio parameters for an inhaler device in use.Instructions 3780 include instructions for extracting, from the accepteddata regarding the medication event for the individual, a timeassociated with the medication event. For example, instructions 3780 caninclude extracting a clock time. Instructions 3790 include instructionsfor comparing the time associated with the medication event with anexpected medication event time for the individual. For example,instructions 3790 can include instructions for comparing the timeassociated with the medication event taken from a clock integrated withthe monitoring device with an expected medication event time for theindividual, such as retrieved from the individual's medication regimen.Instructions 3795 include instructions for saving the comparisons into amemory. For example, instructions 3795 for saving the comparisons into amemory can include saving the comparisons into a computer memory withinthe computer system 120.

As shown in FIG. 37, instructions 3710 include instructions foraccepting data regarding a medication event for an individual. In someembodiments, instructions 3710 include instructions for accepting dataoriginating from a cell phone. For example, the instructions 3710 caninclude instructions for accepting data regarding a medication event foran individual from a monitoring device (e.g. item 110 in FIG. 1) that isa cell phone. In some embodiments, instructions 3710 includeinstructions for accepting data originating from a portable computingdevice. For example, the instructions 3710 can include instructions foraccepting data regarding a medication event for an individual from amonitoring device (e.g. item 110 in FIG. 1) that is a portable computingdevice. In some embodiments, instructions 3710 include instructions foraccepting data originating from a fixed position camera unit. Forexample, the instructions 3710 can include instructions for acceptingdata regarding a medication event for an individual from a monitoringdevice (e.g. item 110 in FIG. 1) that is a fixed position camera unit.In some embodiments, instructions 3710 include instructions foraccepting data originating from a plurality of devices. For example, theinstructions 3710 can include instructions for accepting data regardinga medication event for an individual from a plurality of monitoringdevices (e.g. item 110 in FIG. 1) that can include cell phones, portablecomputing devices (e.g. laptops, table computing devices and PDAs),fixed position camera units, or a combination thereof. In someembodiments, instructions 3710 include instructions for accepting dataoriginating from a micropower impulse radar (MIR) device.

Instructions 3720, as shown in FIG. 37, include instructions forextracting, from the accepted data regarding the medication event forthe individual, one or more identifiers of the medication. In someembodiments, instructions 3720 include instructions for extractingvisual data. For example, instructions 3720 can include instructions forextracting visual data such as visual aspects of the medication (e.g.pill size, color and shape), visual aspects of the medicationadministration devices (e.g. syringe or inhaler) or visual aspects ofthe medication packaging (e.g. box color, logo, bar code or Q code). Insome embodiments, instructions 3720 include instructions for extractingradio frequency identification (RFID) information. For example, amonitoring device (e.g. item 110 in FIG. 1) can receive RFID signalsoriginating from or reflected from a medication or medication packaging,and process this information to be transmitted to the computer system120. The instructions 3720 can include instructions for extracting theradio frequency identification (RFID) information obtained from orreflected from a medication or medication packaging.

Instructions 3730, as shown in FIG. 37, include instructions forcomparing the one or more identifiers of the medication with a set ofstandard medication identifier parameters. In some embodiments,instructions 3730 can include instructions for comparing visualfeatures. For example, instructions 3730 can include instructions forcomparing visual features such as visual features of the medicationitself (e.g. pill size, color and shape), of its administration devices(e.g. syringe or inhaler) or its packaging (e.g. box color, logo, barcode or Q code).

Instructions 3740, as shown in FIG. 37, include instructions forextracting, from the accepted data regarding the medication event forthe individual, the one or more visual features of the medication event.In some embodiments, instructions 3740 include instructions forextracting one or more visual features over time. For example, theinstructions for extracting one or more visual features over time caninclude instructions for extracting one or more visual features from aseries of images taken by a camera over time. For example, theinstructions for extracting one or more visual features over time caninclude instructions for extracting one or more visual features from aseries of images taken by multiple cameras over time. For example, theinstructions for extracting one or more visual features over time caninclude instructions for extracting one or more visual features from avideo.

Instructions 3750, as shown in FIG. 37, include instructions forcomparing the one or more visual features of the medication event withthe set of medication event parameters. In some embodiments,instructions 3750 include: instructions for determining, from a set ofstandard medication event visual features, at least one expected visualfeature; and instructions for comparing the accepted data regarding amedication event for the individual with the determined at least oneexpected visual feature. For example, an expected visual feature caninclude the placement of an inhaler adjacent to an individual's mouth.For example, an expected visual feature can include placement of pillsin the individual's mouth. For example, an expected visual feature caninclude placement of a syringe adjacent to the individual's skin.

Instructions 3760, as shown in FIG. 37, include instructions forextracting, from the accepted data regarding the medication event forthe individual, the one or more non-visual features of the medicationevent. For example, the instructions 3760 can include instructions forextracting one or more non-visual features over time. For example, oneor more features can be extracted from a video (e.g. as a sound overtime). For example, the instructions 3760 can include instructions forextracting one or more audio features. For example, one or more featurescan be extracted from data obtained from a microphone. For example, theinstructions 3760 can include instructions for extracting one or morethermal features. For example, instructions for extracting one or morethermal features can include thermal features of the individual (e.g.skin temperature) or thermal features of a medication administrationdevice (e.g. an inhaler may change temperature during use). For example,the instructions 3760 can include instructions for extracting one ormore features detectable by micropower impulse radar (MIR). See:“Micropower Impulse Radar,” Azevedo and McEwan, Science and TechnologyReview, January/February 1996, pages 17-29; and US Patent ApplicationPublications No. 2004/0249257 and 2004/0249258 to Tupin et al., eachtitled “Article of Manufacture for Extracting Physiological Data UsingUltra-Wideband Radar and Improved Signal Processing Techniques,” whichare all incorporated by reference herein. See also: US PatentApplication Publication No. 2009/0227882 to Foo, titled “Ultra WidebandMonitoring Systems and Antennas,” which is incorporated by referenceherein.

Instructions 3770, as shown in FIG. 37, include instructions forcomparing the one or more non-visual features of the medication eventwith the set of medication event parameters. In some embodiments,instructions 3770 include: instructions for determining, from a set ofstandard medication event non-visual parameters, expected parameters forat least one expected non-visual feature; and instructions for comparingthe accepted data regarding a medication event for the individual withthe expected parameters for at least one expected non-visual feature.For example, instructions 3770 can include: instructions fordetermining, from a set of standard medication event audio parameters,expected audio parameters for at least one expected audio feature, suchas tone or pitch; and instructions for comparing the accepted dataregarding a medication event for the individual with the expectedparameters for at least one expected audio feature. For example,instructions 3770 can include: instructions for determining, from a setof standard medication event thermal parameters, expected parameters forat least one expected thermal feature, such as thermal parameters for anindividual's skin temperature in a region adjacent to an injection; andinstructions for comparing the accepted data regarding a medicationevent for the individual with the expected thermal parameters for atleast one expected thermal feature.

Instructions 3780, as shown in FIG. 37, include instructions forextracting, from the accepted data regarding the medication event forthe individual, the time associated with the medication event. In someembodiments, instructions 3780 include instructions for extracting atime interval associated with the medication event. For example, a timeinterval can include a clock time interval (e.g. between 2:00 and 2:15PM). For example, a time interval can include an elapsed time interval(e.g. 3 hours since the last medication event). For example, a timeinterval can include a time interval relative to another event (e.g.between 1 hour and 2 hours after a meal).

Instructions 3790, as shown in FIG. 37, include instructions forcomparing the time associated with the medication event with theexpected medication event time for the individual. In some embodiments,instructions 3790 include: instructions for determining, from a set ofstandard medication event times, at least one expected medication eventtime; and instructions for comparing the extracted time associated withthe medication event with the determined at least one expectedmedication event time.

Instructions 3795, as shown in FIG. 37, include instructions for savingthe comparisons into a memory. For example, the instructions can besaved into a computer memory within the computer system 120.

In some embodiments, the flowchart illustrated in FIG. 37 includesadditional set of instructions. In some embodiments, thecomputer-readable storage medium including executable instructions formonitoring medication events relating to an individual includes:instructions for determining, from the comparison of the one or moreidentifiers of the medication with the set of standard medicationidentifier parameters, if the one or more identifiers of the medicationare within the set of standard medication identifier parameters. In someembodiments, the computer-readable storage medium including executableinstructions for monitoring medication events relating to an individualincludes: instructions for determining, from the comparison of the oneor more visual features of the medication event with a set of medicationevent parameters, if the one or more visual features of the medicationevent are within the set of medication event parameters. In someembodiments, the computer-readable storage medium including executableinstructions for monitoring medication events relating to an individualincludes: instructions for determining, from the comparison of the oneor more non-visual features of the medication event with the set ofmedication event parameters, if the one or more non-visual features ofthe medication event are within the set of medication event parameters.In some embodiments, the computer-readable storage medium includingexecutable instructions for monitoring medication events relating to anindividual includes: instructions for determining, from the comparisonof the time associated with the medication event with the expectedmedication event time for the individual, if the time associated withthe medication event is within the expected medication event time forthe individual. In some embodiments, the computer-readable storagemedium including executable instructions for monitoring medicationevents relating to an individual includes: instructions for saving oneor more of the comparisons into a medical record for the individual. Forexample, a medical record can be stored in computer memory on thecomputer system (e.g. 120 of FIG. 1). In some embodiments, thecomputer-readable storage medium including executable instructions formonitoring medication events relating to an individual includes:instructions for determining, from the comparisons, a medicationcompliance score for the medication event. In some embodiments, thecomputer-readable storage medium including executable instructions formonitoring medication events relating to an individual includes:instructions for indicating one or more of the comparisons. For example,instructions for indicating one or more of the comparisons can includeindicating on a display device attached to the computer system (e.g. 120of FIG. 1). In some embodiments, the computer-readable storage mediumincluding executable instructions for monitoring medication eventsrelating to an individual includes: instructions for activating,depending on one or more of the comparisons, an alert indicator. Forexample, instructions for instructions for activating, depending on oneor more of the comparisons, an alert indicator can include an alertindicator (such as a light or a sound emitter device) attached to thecomputer system (e.g. 120 of FIG. 1).

In some embodiments, the computer-readable storage medium includingexecutable instructions for monitoring medication events relating to anindividual includes: instructions for accepting data regarding a secondmedication event for the individual; instructions for extracting, fromthe accepted data regarding the second medication event for theindividual, one or more identifiers of the medication; instructions forcomparing the one or more identifiers of the medication with the set ofstandard medication identifier parameters; instructions for extracting,from the accepted data regarding the second medication event for theindividual, one or more visual features of the medication event;instructions for comparing the one or more visual features of the secondmedication event with the set of medication event parameters;instructions for extracting, from the accepted data regarding the secondmedication event for the individual, one or more non-visual features ofthe second medication event; instructions for comparing the one or morenon-visual features of the second medication event with the set ofmedication event parameters; instructions for extracting, from theaccepted data regarding the second medication event for the individual,a time associated with the second medication event; instructions forcomparing the time associated with the second medication event with anexpected second medication event time for the individual; andinstructions for saving the comparisons associated with the secondmedication event into a memory. In some embodiments, the instructionsinclude: instructions for determining, from the saved comparisonsassociated with the medication event and the comparisons associated withthe second medication event, if the medication events meet at least onestandard; and instructions for activating an indicator in response tothe determination.

FIG. 38 illustrates a flowchart of a method 3800 for monitoringmedication events. These method steps can be carried out, for example,by a computer system (e.g. item 120 in FIG. 1). FIG. 38 shows that themethod includes a series of steps, 3810, 3820, 3830, 3840, 3850, 3860,3870, 3880, 3890, 3895. Method step 3810 includes accepting dataregarding a medication event for an individual. For example, a computersystem (e.g. item 120 in FIG. 1) can accept data transmitted from amonitoring device (e.g. item 110 in FIG. 1). Method step 3820 includesextracting, from the accepted data regarding the medication event forthe individual, one or more identifiers of the medication. Method step3830 includes comparing the one or more identifiers of the medicationwith a set of standard medication identifier parameters. Method step3840 includes extracting, from the accepted data regarding themedication event for the individual, one or more visual features of themedication event. Method step 3850 includes comparing the one or morevisual features of the medication event with a set of medication eventparameters. Method step 3860 includes extracting, from the accepted dataregarding the medication event for the individual, one or morenon-visual features of the medication event. Method step 3870 includescomparing the one or more non-visual features of the medication eventwith the set of medication event parameters. Method step 3880 includesextracting, from the accepted data regarding the medication event forthe individual, a time associated with the medication event. Method step3890 includes comparing the time associated with the medication eventwith an expected medication event time for the individual. Method step3895 includes saving the comparisons into a memory.

As shown in FIG. 38, method step 3810 includes accepting data regardinga medication event for an individual. In some embodiments, method step3810 can include accepting data originating from a cell phone. In someembodiments, method step 3810 can include accepting data originatingfrom a portable computing device. In some embodiments, method step 3810can include accepting data originating from a fixed position cameraunit. In some embodiments, method step 3810 can include accepting dataoriginating from a plurality of devices. For example, a computer system(e.g. 120 in FIG. 1) can accept data regarding a medication event for anindividual from a monitoring device (e.g. 110 in FIG. 1). The monitoringdevice can include one or more of a cell phone, a portable computingdevice (e.g. a laptop, tablet computer, or PDA). In some embodiments,method step 3810 can include accepting data originating from amicropower impulse radar (MIR) device. See: “Micropower Impulse Radar,”Azevedo and McEwan, Science and Technology Review, January/February1996, pages 17-29; and US Patent Application Publications No.2004/0249257 and 2004/0249258 to Tupin et al., each titled “Article ofManufacture for Extracting Physiological Data Using Ultra-Wideband Radarand Improved Signal Processing Techniques,” which are all incorporatedby reference herein. See also: US Patent Application Publication No.2009/0227882 to Foo, titled “Ultra Wideband Monitoring Systems andAntennas,” which is incorporated by reference herein.

FIG. 38 illustrates that method step 3820 includes extracting, from theaccepted data regarding the medication event for the individual, one ormore identifiers of the medication. In some embodiments, method step3820 includes extracting visual data. For example, method step 3820 caninclude extracting visual data from data generated by a cameraintegrated into a computing device (e.g. a laptop, smartphone, PDA ortablet computer). In some embodiments, method step 3820 includesextracting radio frequency identification (RFID) information. Forexample, the accepted data regarding the medication event for theindividual can include data obtained from a RFID signal originating fromor reflected by a RFID tag included with a medication or medicationpackaging.

FIG. 38 shows that method step 3830 includes comparing the one or moreidentifiers of the medication with a set of standard medicationidentifier parameters. In some embodiments, method step 3830 includescomparing visual features. For example, the method can include comparingvisual features such as visual features of the medication (e.g. pillcolor, size and shape) or visual features of the medicationadministration devices (e.g. syringe or inhaler) or visual features ofthe medication packaging (e.g. color, logo, or shape).

FIG. 38 shows that method step 3840 includes extracting, from theaccepted data regarding a medication event for the individual, one ormore visual features of the medication event. In some embodiments,method step 3840 includes extracting one or more visual features overtime. For example, method step 3840 can include extracting one or morevisual features over time, such as from a series of images or a videorecorded by a camera unit.

FIG. 38 depicts that method step 3850 includes comparing the one or morevisual features of the medication event with a set of medication eventparameters. In some embodiments, method step 3850 includes: determining,from a set of standard medication event visual features, at least oneexpected visual feature; and comparing the accepted data regarding amedication event for the individual with the determined at least oneexpected visual feature.

FIG. 38 illustrates that method step 3860 includes extracting, from theaccepted data regarding a medication event for the individual, one ormore non-visual features of the medication event. In some embodiments,method step 3860 includes extracting one or more non-visual featuresover time. For example, method step 3860 can include extracting audiofeatures from an audio recording over time. In some embodiments, methodstep 3860 includes extracting one or more audio features. For example,method step 3860 can include extracting audio features recorded by amicrophone device integrated in the monitoring device (e.g. item 110 inFIG. 1). For example, method step 3860 can include extracting one ormore near-infrared (IR) features. For example, method step 3860 caninclude extracting one or more thermal features. For example, methodstep 3860 can include extracting one or more features detectable bymicropower impulse radar (MIR).

FIG. 38 shows that method step 3870 includes comparing the one or morenon-visual features of the medication event with a set of medicationevent parameters. In some embodiments, method step 3870 includes:determining, from a set of standard medication event non-visualparameters, expected parameters for at least one expected non-visualfeature; and comparing the accepted data regarding a medication eventfor the individual with the expected parameters for at least oneexpected non-visual feature.

FIG. 38 shows that method step 3880 includes extracting, from theaccepted data regarding a medication event for the individual, a timeassociated with the medication event. In some embodiments, method step3880 includes extracting a clock time associated with the medicationevent. For example, method step 3880 can extract a clock time such as“3:45 PM.” In some embodiments, method step 3880 includes extracting atime interval associated with the medication event. For example, methodstep 3880 can extract a clock time interval, such as “between 10:00 AMand 10:10 AM.” For example, method step 3880 can extract an elapsed timeinterval, such as “the audio recording of the inhaler sound lasted 30seconds.” For example, method step 3880 can extract an elapsed timeinterval, such as “there was 5 minutes between the injection ofmedication A and the swallowing of medication B.”

FIG. 38 shows that method step 3890 includes comparing the timeassociated with the medication event with an expected medication eventtime for the individual. In some embodiments, method step 3890 includes:determining, from a set of standard medication event times, at least oneexpected medication event time; and comparing the extracted timeassociated with the medication event with the determined at least oneexpected medication event time.

FIG. 38 shows that method step 3895 includes saving the comparisons intoa memory. For example, method step 3895 can include saving thecomparisons into a memory in a computer system (e.g. item 120 in FIG.1).

In some embodiments, there are one or more additional steps to themethod illustrated in FIG. 38. For example, the method for monitoringmedication events can include determining, from the comparison of theone or more identifiers of the medication with the set of standardmedication identifier parameters, if the one or more identifiers of themedication are within the set of standard medication identifierparameters. For example, the method for monitoring medication events caninclude determining, from the comparison of the one or more visualfeatures of the medication event with a set of medication eventparameters, if the one or more visual features of the medication eventare within the set of medication event parameters. For example, themethod for monitoring medication events can include determining, fromthe comparison of the one or more non-visual features of the medicationevent with the set of medication event parameters, if the one or morenon-visual features of the medication event are within the set ofmedication event parameters. For example, the method for monitoringmedication events can include determining, from the comparison of thetime associated with the medication event with the expected medicationevent time for the individual, if the time associated with themedication event is within the expected medication event time for theindividual. For example, the method for monitoring medication events caninclude saving one or more of the comparisons into a medical record forthe individual. For example, method for monitoring medication events caninclude saving the comparisons into medical record for the individual ina memory in a computer system (e.g. item 120 in FIG. 1). For example,the method for monitoring medication events can include determining,from the comparisons, a medication compliance score for the medicationevent. A medication compliance score can be saved in memory, such asinto a memory in a computer system (e.g. item 120 in FIG. 1). Amedication compliance score can be displayed, such as with a displaydevice attached to the computer system (e.g. item 120 in FIG. 1). Forexample, the method for monitoring medication events can includeindicating one or more of the comparisons. One or more of thecomparisons can be indicated on a device attached to the computer system(e.g. item 120 in FIG. 1), or on a monitoring device (e.g. item 110 inFIG. 1). For example, the method for monitoring medication events caninclude activating, depending on one or more of the comparisons, analert indicator. An alert indicator, for example, can be attached to thecomputer system (e.g. item 120 in FIG. 1).

For example, the method for monitoring medication events can include:accepting data regarding a second medication event for the individual;extracting, from the accepted data regarding the second medication eventfor the individual, one or more identifiers of the medication; comparingthe one or more identifiers of the medication with a set of standardmedication identifier parameters; extracting, from the accepted dataregarding the second medication event for the individual, one or morevisual features of the medication event; comparing the one or morevisual features of the second medication event with a set of medicationevent parameters; extracting, from the accepted data regarding thesecond medication event for the individual, one or more non-visualfeatures of the second medication event; comparing the one or morenon-visual features of the second medication event with the set ofmedication event parameters; extracting, from the accepted dataregarding the second medication event for the individual, a timeassociated with the second medication event; comparing the timeassociated with the second medication event with an expected secondmedication event time for the individual; and saving the comparisonsassociated with the second medication event into a memory. The methodcan also include: determining, from the saved comparisons associatedwith the medication event and the comparisons associated with the secondmedication event, if the medication events meet at least one standard;and activating an indicator in response to the determination.

FIG. 39 illustrates diagram of aspects of a system for monitoringmedication events. The system can be a computer system such as depictedin FIG. 1 and described herein. The system 3900 depicted in FIG. 39includes electrical circuitry. The circuitry of the system 3900 isconfigured to carry out a series of logical processes. As illustrated inFIG. 39, a system 3900 for monitoring medication events relating to anindividual includes one or more circuitry components 3910, 3920, 3930,3940, 3950, 3960, 3970. The circuitry is configured to carry outspecific processes.

The system 3900 includes circuitry 3910 for associating a time intervalwith a first medication event for an individual. The system 3900includes circuitry 3920 for identifying a start of the time intervalassociated with the first medication event. The system 3900 includescircuitry 3930 for activating an indicator in response to theidentification of the start of the time interval associated with thefirst medication event. The system 3900 includes circuitry 3940 foractivating at least one camera unit associated with the individual, theactivating in response to the identification of the start of the timeinterval associated with the first medication event. The system 3900includes circuitry 3950 for identifying an end of the time intervalassociated with the first medication event. The system 3900 includescircuitry 3960 for accepting data relating to the time intervalassociated with the first medication event from the at least one cameraunit. The system 3900 includes circuitry 3970 for deactivating the atleast one camera unit in response to the identification of the end ofthe time interval associated with the first medication event.

FIG. 40 illustrates aspects of the system 3900 shown in FIG. 39. FIG. 40shows that, in some embodiments, circuitry 3910 for associating the timeinterval with the first medication event for the individual includes oneor more of circuitry 4000, 4010. In some embodiments, circuitry 3910includes circuitry 4000 for associating a clock time interval with thefirst medication event. For example, circuitry for associating a clocktime interval with the first medication event can include associatingthat the medication event lasted from a clock time to another clocktime, such as from 9:45 to 10:00 AM. In some embodiments, circuitry 3910includes circuitry 4010 for associating an elapsed time interval withthe first medication event. For example, circuitry 4010 can associate anelapsed time interval from a prior event with the first medicationevent, such as the elapsed time interval from an individual's priormeal.

FIG. 40 also illustrates that, in some embodiments, circuitry 3920 foridentifying a start of the time interval associated with the firstmedication event includes one or more of circuitry 4020, 4030. Circuitry4020 includes circuitry for identifying the start of a clock timeinterval associated with the first medication event. For example,circuitry 4020 can identify that the first medication event started at10:00 AM and had a duration of 5 minutes. Circuitry 4030 includescircuitry for identifying the start of an elapsed time intervalassociated with the first medication event. For example, circuitry 4020can identify that the first medication event started 2 hours afteranother event, such as 2 hours since the individual drank a glass ofwater.

FIG. 40 also illustrates that, in some embodiments, circuitry 3930 foractivating the indicator in response to the identification of the startof the time interval associated with the first medication event includescircuitry 4040, 4050, 4060. Circuitry 4040 includes circuitry foractivating a visual indicator. For example, a system 3900 can includecircuitry 4040 for activating a visual indicator attached to a computersystem (e.g. item 120 in FIG. 1) or a visual indicator integrated into amonitoring device (e.g. item 110 in FIG. 1) in response to theidentification of the start of the time interval associated with thefirst medication event. Circuitry 4050 includes circuitry for activatingan auditory indicator. For example, a system 3900 can include circuitry4040 for activating an auditory indicator attached to a computer system(e.g. item 120 in FIG. 1) or an auditory indicator integrated into amonitoring device (e.g. item 110 in FIG. 1) in response to theidentification of the start of the time interval associated with thefirst medication event. Circuitry 4060 includes circuitry for activatinga vibratory indicator. For example, a system 3900 can include circuitry4060 for activating a vibratory indicator attached to a computer system(e.g. item 120 in FIG. 1) or a vibratory indicator integrated into amonitoring device (e.g. item 110 in FIG. 1) in response to theidentification of the start of the time interval associated with thefirst medication event.

FIG. 41 depicts aspects of the system 3900 illustrated in FIG. 39. FIG.41 shows that, in some embodiments, circuitry 3940 for activating the atleast one camera unit associated with the individual, the activating inresponse to the identification of the start of the time intervalassociated with the first medication event includes one or more ofcircuitry 4100, 4110, 4120, 4130, 4140. Circuitry 4100 includescircuitry for activating at least one camera unit within a mobile phone.For example, circuitry 4100 can include circuitry for activating atleast one camera unit within a mobile phone integrated into a monitoringdevice (e.g. item 110 in FIG. 1). Circuitry 4110 includes circuitry foractivating at least one camera unit within a portable computing device.For example, circuitry 4110 can include circuitry for activating atleast one camera unit within a portable computing device used as amonitoring device (e.g. item 110 in FIG. 1). Circuitry 4120 includescircuitry for activating at least one camera unit within a fixedposition camera unit. For example, circuitry 4120 can include circuitryfor activating a fixed position camera unit integrated into a monitoringdevice (e.g. item 110 in FIG. 1). Circuitry 4130 includes circuitry foractivating a plurality of camera units. For example, circuitry 4130 caninclude circuitry for activating at least two of: camera unit within acell phone, a camera unit within a portable computing device, or a fixedposition camera unit. Circuitry 4140 includes circuitry for activatingthe at least one camera unit including activating non-visual componentsof the at least one camera unit. For example, circuitry 4140 can includeactivating a MIR integrated into a laptop computer.

FIG. 42 shows aspects of the system 3900 illustrated in FIG. 39. FIG. 4s shows that, in some embodiments, circuitry 3940 for activating the atleast one camera unit associated with the individual, the activating inresponse to the identification of the start of the time intervalassociated with the first medication event includes one or more ofcircuitry 4200, 4210, 4220, 4230, 4240. Circuitry 4200 includescircuitry for activating at least one camera unit including amicrophone. For example, circuitry 4200 can include circuitry foractivating at least one camera unit including a microphone integratedinto a portable computing device. Circuitry 4210 includes circuitry foractivating at least one camera unit including a RFID detector. Forexample, circuitry 4210 can include circuitry for activating at leastone camera unit including a RFID detector integrated into a monitoringdevice (e.g. item 110 in FIG. 1). Circuitry 4220 includes circuitry foractivating the at least one camera unit for video data acquisition.Circuitry 4230 includes circuitry for activating the at least one cameraunit for a series of data acquisition events. For example, a camera unitcan be activated to obtain images every 5 seconds for a period of timecorresponding to the expected time of the medication event. Circuitry4240 includes circuitry for activating the at least one camera unit fordata acquisition including near-infrared (IR) data.

FIG. 43 illustrates aspects of the system 3900 illustrated in FIG. 39.FIG. 43 shows that, in some embodiments, circuitry 3940 for activatingthe at least one camera unit associated with the individual, theactivating in response to the identification of the start of the timeinterval associated with the first medication event includes one or moreof circuitry 4300, 4310. Circuitry 4300 includes circuitry foractivating the at least one camera unit for data acquisition includingthermal data. Circuitry 4310 includes circuitry for activating at leastone micropower impulse radar (MIR) device.

FIG. 43 also depicts that, in some embodiments, circuitry 3950 foridentifying the end of the time interval associated with the firstmedication event includes one or more of circuitry 4320, 4330. Circuitry4320 includes circuitry for associating a clock time interval with theend of the time interval associated with the first medication event. Forexample, circuitry 4320 can include circuitry for associating a clocktime of 10:15 to 10:20 AM with the end of the time interval associatedwith the first medication event. Circuitry 4330 includes circuitry forassociating an elapsed time interval with the end of the time intervalassociated with the first medication event. For example, circuitry 4330can include circuitry for associating the end of a 20 minute intervalwith the end of the time interval associated with the first medicationevent.

FIG. 44 depicts aspects of the system 3900 illustrated in FIG. 39. FIG.44 illustrates that, in some embodiments, circuitry 3960 for acceptingdata relating to the time interval associated with the first medicationevent from the at least one camera unit includes one or more ofcircuitry 4400,4410. Circuitry 4400 includes circuitry for acceptingdata generated by the at least one camera unit during the time intervalassociated with the first medication event. Circuitry 4410 includescircuitry for accepting data relating to the time interval associatedwith the first medication event from each of a plurality of cameraunits.

FIG. 44 also shows that, in some embodiments, circuitry 3970 fordeactivating the at least one camera unit in response to theidentification of the end of the time interval associated with the firstmedication event includes one or more of circuitry 4420, 4430. Circuitry4420 includes circuitry for deactivating at least one camera unit withina mobile phone. Circuitry 4430 includes circuitry for deactivating atleast one camera unit within a portable computing device.

FIG. 45 illustrates aspects of the system 3900 shown in FIG. 39. FIG. 45depicts that, in some embodiments, circuitry 3970 for deactivating theat least one camera unit in response to the identification of the end ofthe time interval associated with the first medication event includesone or more of circuitry 4500, 4510. Circuitry 4500 includes circuitryfor deactivating at least one camera unit within a fixed position cameraunit. Circuitry 4510 includes circuitry for deactivating a plurality ofcamera units.

FIG. 45 also illustrates that, in some embodiments, the system depictedin FIG. 39 includes one or more of circuitry 4520, 4530. Circuitry 4520includes circuitry for activating an indicator in response to thecircuitry for accepting data relating to the time interval associatedwith the first medication event from the at least one camera unit. Forexample, circuitry 4520 can include circuitry for activating anindicator attached to the computer system (e.g. item 120 in FIG. 1) inresponse to the circuitry for accepting data relating to the timeinterval associated with the first medication event from the at leastone camera unit. Circuitry 4530 includes circuitry for saving theaccepted data relating to the time interval associated with the firstmedication event from the at least one camera unit into a memory. Forexample, circuitry 4520 can include circuitry for saving the accepteddata relating to the time interval associated with the first medicationevent from the at least one camera unit into a memory attached to thecomputer system (e.g. item 120 in FIG. 1).

FIG. 46 depicts that, in some embodiments, the system shown in FIG. 39includes one or more of circuitry 4600, 4610, 4620. Circuitry 4600includes: circuitry for processing the accepted data relating to thetime interval associated with the first medication event from the atleast one camera unit into a transmission; and circuitry fortransmitting the processed data. For example, the computer system (e.g.item 120 in FIG. 1) can transmit the processed data to another computingdevice. Circuitry 4610 includes circuitry for activating an indicator inresponse to the identification of the end of the time intervalassociated with the first medication event. For example, a computersystem (e.g. item 120 in FIG. 1) can include an attached indicatordevice. Circuitry 4620 includes: circuitry for retrieving at least oneattribute of the individual from memory; circuitry for examining theaccepted data for the at least one attribute of the individual;circuitry for forming an identification result for the individual fromthe examination; and circuitry for transmitting the identificationresult for the individual.

FIG. 47 illustrates that, in some embodiments, the system shown in FIG.39 includes one or more of circuitry 4700, 4710. Circuitry 4700includes: circuitry for retrieving at least one attribute of themedication from memory; circuitry for examining the accepted data forthe at least one attribute of the medication; circuitry for forming anidentification result for the medication from the examination; andcircuitry for transmitting the identification result for the medication.Circuitry 4710 includes circuitry for initiating a transmission inresponse to the identification of the start of the time intervalassociated with the first medication event.

FIG. 48 shows that, in some embodiments, the system depicted in FIG. 39includes circuitry 4800. Circuitry 4800 includes: circuitry forassociating a second time interval with a second medication event forthe individual; circuitry for identifying a start of the second timeinterval associated with the second medication event; circuitry foractivating an indicator in response to the identification of the startof the second time interval associated with the second medication event;circuitry for activating at least one camera unit associated with theindividual, the activating in response to the identification of thestart of the second time interval associated with the second medicationevent; circuitry for identifying an end of the second time intervalassociated with the second medication event; circuitry for acceptingdata relating to the second time interval associated with the secondmedication event from the at least one camera unit; and circuitry fordeactivating the at least one camera unit in response to theidentification of the end of the second time interval associated withthe second medication event.

FIG. 49 shows that, in some embodiments, the system illustrated in FIG.39 includes circuitry 4900, 4910. Circuitry 4900 includes: circuitry forcomparing the time interval associated with the first medication eventand the second time interval associated with the second medication eventwith a standard time interval; and circuitry for activating an indicatorif either the time interval associated with the first medication eventor the second time interval associated with the second medication eventare distinct from the standard time interval. In some embodiments,circuitry 4900 is included within circuitry 4800, described above.Circuitry 4910 includes: circuitry for comparing the accepted datarelating to the time interval associated with the first medication eventwith the set of standard medication event parameters; circuitry forcomparing the accepted data relating to the second time intervalassociated with the second medication event with a set of standardmedication event parameters; and circuitry for activating an indicatorif either the accepted data relating to the time interval associatedwith the first medication event or the accepted data relating to thesecond time interval associated with the second medication event aredistinct from the set of standard medication event parameters.

FIG. 50 shows aspects of a computer system 120 including at least onemain computing unit 125. Although a single main computing unit 125 isillustrated in FIG. 50, in some embodiments there may be a plurality ofmain computing units 125. A main computing unit 125 includescomputer-readable storage medium including executable instructions formonitoring medication events 5000. The computer-readable storage mediumincluding executable instructions for monitoring medication events 5000includes instructions 5010, 5020, 5030, 5040, 5050, 5060, 5070.Instructions 5010 include instructions for associating a time intervalwith a first medication event for an individual. Instructions 5020include instructions for identifying a start of the time intervalassociated with the first medication event. Instructions 5030 includeinstructions for activating an indicator in response to theidentification of the start of the time interval associated with thefirst medication event. Instructions 5040 include instructions foractivating at least one camera unit associated with the individual, theactivating in response to the identification of the start of the timeinterval associated with the first medication event. Instructions 5050include instructions for identifying an end of the time intervalassociated with the first medication event. Instructions 5060 includeinstructions for accepting data relating to the time interval associatedwith the first medication event from the at least one camera unit.Instructions 5070 include instructions for deactivating the at least onecamera unit in response to the identification of the end of the timeinterval associated with the first medication event.

Instructions 5010 include instructions for associating a time intervalwith a first medication event for an individual. In some embodiments,instructions 5010 include additional instructions. For example, in someembodiments, instructions 5010 include instructions for associating aclock time interval with the first medication event. For example, insome embodiments, instructions 5010 include instructions for associatingan elapsed time interval with the first medication event.

Instructions 5020 include the instructions for identifying the start ofthe time interval associated with the first medication event. In someembodiments, instructions 5020 include additional instructions. Forexample, in some embodiments, instructions 5020 include instructions foridentifying the start of a clock time interval associated with the firstmedication event. For example, in some embodiments, instructions 5020include instructions for identifying the start of an elapsed timeinterval associated with the first medication event.

Instructions 5030 include the instructions for activating the indicatorin response to the identification of the start of the time intervalassociated with the first medication event. In some embodiments,instructions 5030 include additional instructions. For example, in someembodiments, instructions 5030 include instructions for activating avisual indicator. For example, the instructions 5030 can lead to theactivation of a visible indicator, such as a light, attached to thecomputer system (e.g. item 120 in FIG. 1). In some embodiments,instructions 5030 include instructions for activating an auditoryindicator. For example, the instructions 5030 can lead to the activationof an auditory indicator, such as a buzzer, attached to the computersystem (e.g. item 120 in FIG. 1). In some embodiments, instructions 5030include instructions for activating an vibratory indicator. For example,the instructions 5030 can lead to the activation of an vibratoryindicator, such as to result in the vibration of a component attached tothe computer system (e.g. item 120 in FIG. 1).

Instructions 5040 include the instructions for activating the at leastone camera unit associated with the individual, the activating inresponse to the identification of the start of the time intervalassociated with the first medication event. In some embodiments,instructions 5040 include additional instructions. For example, in someembodiments, instructions 5040 include instructions for activating atleast one camera unit within a mobile phone. For example, theinstructions 5040 can be processed into a transmission to a mobile phonethat is a monitoring device (e.g. as item 110 in FIG. 1). In someembodiments, instructions 5040 can include instructions for activatingat least one camera unit within a portable computing device. Forexample, the instructions 5040 can be processed into a transmission to aportable computing device (e.g. a laptop, a tablet computer, or a PDA)that is a monitoring device (e.g. as item 110 in FIG. 1). In someembodiments, instructions 5040 can include instructions for activatingat least one camera unit within a fixed position camera unit. Forexample, the instructions 5040 can be processed into a transmission to afixed position camera unit, such as a camera unit that is affixed to awall at a location, that is a monitoring device (e.g. as item 110 inFIG. 1). In some embodiments, instructions 5040 can include instructionsfor activating plurality of camera units. For example, the instructions5040 can be processed into a transmission to a plurality of monitoringdevices (e.g. as item 110 in FIG. 1) including camera units. In someembodiments, instructions 5040 can include instructions activating theat least one camera unit including activating non-visual components ofthe at least one camera unit. For example, the instructions 5040 can beprocessed into a transmission to a portable computing device (e.g. alaptop, a tablet computer, or a PDA) that is a monitoring device (e.g.as item 110 in FIG. 1) and which includes non-visual components, such asa microphone, a RFID transceiver, or a micropoer impulse radar (MIR)device. In some embodiments, instructions 5040 can include instructionsfor activating at least one camera unit including a microphone. Forexample, the instructions 5040 can be processed into a transmission to acell phone (e.g. a laptop, a tablet computer, or a PDA) that is amonitoring device (e.g. as item 110 in FIG. 1) leading to the activationof a microphone in the cell phone. In some embodiments, instructions5040 can include instructions for activating at least one camera unitincluding a RFID detector. For example, the instructions 5040 can beprocessed into a transmission to a portable computing device (e.g. alaptop, a tablet computer, or a PDA) that is a monitoring device (e.g.as item 110 in FIG. 1) and that includes an RFID detector, resulting inthe activation of the RFID detector. In some embodiments, instructions5040 can include instructions for activating the at least one cameraunit for video data acquisition. For example, the instructions 5040 canbe processed into a transmission to a cell phone that is a monitoringdevice (e.g. as item 110 in FIG. 1) and resulting in the activation ofvideo data acquisition by the cell phone. In some embodiments,instructions 5040 can include instructions activating the at least onecamera unit for a series of data acquisition events. For example, theinstructions 5040 can be processed into a transmission to a cell phonethat is a monitoring device (e.g. as item 110 in FIG. 1) resulting inthe activation of a camera in the cell phone for a series of short videorecordings (e.g. a series of 100 events, each of 2 second duration)being taken by the cell phone camera. In some embodiments, instructions5040 can include instructions for activating the at least one cameraunit for data acquisition including near-infrared (IR) data. Forexample, the instructions 5040 can be processed into a transmission to aportable computing device (e.g. a laptop, a tablet computer, or a PDA)that is a monitoring device (e.g. as item 110 in FIG. 1) which resultsin the activation of a near-IR reader in the portable computing device.In some embodiments, instructions 5040 can include instructions foractivating the at least one camera unit for data acquisition includingthermal data. For example, the instructions 5040 can be processed into atransmission to a portable computing device (e.g. a laptop, a tabletcomputer, or a PDA) that is a monitoring device (e.g. as item 110 inFIG. 1) which results in the activation of a thermal reader in theportable computing device In some embodiments, instructions 5040 caninclude instructions for activating at least one micropower impulseradar (MIR) device. For example, the instructions 5040 can be processedinto a transmission to a portable computing device (e.g. a laptop, atablet computer, or a PDA) that is a monitoring device (e.g. as item 110in FIG. 1) and that includes a MIR device, resulting in the activationof the MIR device.

Instructions 5050 include the instructions for identifying the end ofthe time interval associated with the first medication event. In someembodiments, instructions 5050 include additional instructions. Forexample, in some embodiments, instructions 5050 include instructions forassociating a clock time interval with the end of the time intervalassociated with the first medication event. For example, in someembodiments instructions 5050 include instructions for associating anelapsed time interval with the end of the time interval associated withthe first medication event.

Instructions 5060 include the instructions for accepting data relatingto the time interval associated with the first medication event from theat least one camera unit. In some embodiments, instructions 5060 includeadditional instructions. For example, in some embodiments, instructions5060 include instructions for accepting data generated by the at leastone camera unit during the time interval associated with the firstmedication event. For example, in some embodiments, instructions 5060include instructions for accepting data relating to the time intervalassociated with the first medication event from each of a plurality ofcamera units.

Instructions 5070 include the instructions for deactivating the at leastone camera unit in response to the identification of the end of the timeinterval associated with the first medication event. In someembodiments, instructions 5070 include additional instructions. Forexample, in some embodiments, instructions 5070 include instructions fordeactivating at least one camera unit within a mobile phone. Forexample, in some embodiments, instructions 5070 include instructions fordeactivating at least one camera unit within a portable computingdevice. For example, in some embodiments, instructions 5070 includeinstructions for deactivating at least one camera unit within a fixedposition camera unit. For example, in some embodiments, instructions5070 include instructions for deactivating a plurality of camera units.

In some embodiments, the computer-readable storage medium 5000 includingexecutable instructions for monitoring medication events includesinstructions in addition to instructions 5010, 5020, 5030, 5040, 5050,5060, 5070. In some embodiments, the computer-readable storage medium5000 including executable instructions for monitoring medication eventsincludes instructions for activating an indicator in response to theinstructions for accepting data relating to the time interval associatedwith the first medication event from the at least one camera unit. Insome embodiments, the computer-readable storage medium 5000 includingexecutable instructions for monitoring medication events includesinstructions for saving the accepted data relating to the time intervalassociated with the first medication event from the at least one cameraunit into a memory. In some embodiments, the computer-readable storagemedium 5000 including executable instructions for monitoring medicationevents includes: instructions for processing the accepted data relatingto the time interval associated with the first medication event from theat least one camera unit into a transmission; and instructions fortransmitting the processed data. In some embodiments, thecomputer-readable storage medium 5000 including executable instructionsfor monitoring medication events includes instructions activating anindicator in response to the identification of the end of the timeinterval associated with the first medication event. In someembodiments, the computer-readable storage medium 5000 includingexecutable instructions for monitoring medication events includes:instructions for retrieving at least one attribute of the individualfrom memory; instructions for examining the accepted data for the atleast one attribute of the individual; instructions for forming anidentification result for the individual from the examination; andinstructions for transmitting the identification result for theindividual. In some embodiments, the computer-readable storage medium5000 including executable instructions for monitoring medication eventsincludes: instructions for retrieving at least one attribute of themedication from memory; instructions for examining the accepted data forthe at least one attribute of the medication; instructions for formingan identification result for the medication from the examination; andinstructions for transmitting the identification result for themedication. In some embodiments, the computer-readable storage medium5000 including executable instructions for monitoring medication eventsincludes instructions for initiating a transmission in response to theidentification of the start of the time interval associated with thefirst medication event. In some embodiments, the computer-readablestorage medium 5000 including executable instructions for monitoringmedication events includes: instructions for comparing the accepted datarelating to the time interval associated with the first medication eventwith a set of standard medication event parameters; instructions forcomparing the accepted data relating to the second time intervalassociated with the second medication event with the set of standardmedication event parameters; and instructions for activating anindicator if either the accepted data relating to the time intervalassociated with the first medication event or the accepted data relatingto the second time interval associated with the second medication eventare distinct from the set of standard medication event parameters.

In some embodiments, the computer-readable storage medium 5000 includingexecutable instructions for monitoring medication events includes:instructions for identifying a start of the second time intervalassociated with the second medication event; instructions for activatingan indicator in response to the identification of the start of thesecond time interval associated with the second medication event;instructions for activating at least one camera unit associated with theindividual, the activating in response to the identification of thestart of the second time interval associated with the second medicationevent; instructions for identifying an end of the second time intervalassociated with the second medication event; instructions for acceptingdata relating to the second time interval associated with the secondmedication event from the at least one camera unit; and instructions fordeactivating the at least one camera unit in response to theidentification of the end of the second time interval associated withthe second medication event. In some embodiments, these instructionsalso include: instructions for comparing the time interval associatedwith the first medication event and the second time interval associatedwith the second medication event with a standard time interval; andinstructions for activating an indicator if either the time intervalassociated with the first medication event or the second time intervalassociated with the second medication event are distinct from thestandard time interval.

FIG. 51 illustrates aspects of a method for monitoring medicationevents. FIG. 51 illustrates a flowchart of the method. Block 5100illustrates that the method is for monitoring medication event. Block5100 includes blocks 5110, 5120, 5130, 5140, 5150, 5160, 5170. Block5110 shows associating a time interval with a first medication event foran individual. Block 5120 illustrates identifying a start of the timeinterval associated with the first medication event. Block 5130 depictsactivating an indicator in response to the identification of the startof the time interval associated with the first medication event. Block5140 shows activating at least one camera unit associated with theindividual, the activating in response to the identification of thestart of the time interval associated with the first medication event.Block 5150 illustrates identifying an end of the time intervalassociated with the first medication event. Block 5160 shows acceptingdata relating to the time interval associated with the first medicationevent from the at least one camera unit. Block 5170 shows deactivatingthe at least one camera unit in response to the identification of theend of the time interval associated with the first medication event.

In some embodiments, the method includes further steps that can berepresented in the flowchart format of FIG. 51. For example, block 5110shows associating a time interval with a first medication event for anindividual. In some embodiments, block 5110 can include associating aclock time interval with the first medication event. In someembodiments, block 5110 can include associating an elapsed time intervalwith the first medication event.

Block 5120 illustrates identifying a start of the time intervalassociated with the first medication event. In some embodiments, block5120 includes identifying the start of a clock time interval associatedwith the first medication event. In some embodiments, block 5120includes identifying the start of an elapsed time interval associatedwith the first medication event.

Block 5130 depicts activating an indicator in response to theidentification of the start of the time interval associated with thefirst medication event. In some embodiments, block 5130 can includeactivating a visual indicator. In some embodiments, block 5130 caninclude activating an auditory indicator. In some embodiments, block5130 can include activating a vibratory indicator.

Block 5140 shows activating at least one camera unit associated with theindividual, the activating in response to the identification of thestart of the time interval associated with the first medication event.In some embodiments, block 5140 includes activating at least one cameraunit within a mobile phone. In some embodiments, block 5140 includesactivating at least one camera unit within a portable computing device.In some embodiments, block 5140 includes activating at least one cameraunit within a fixed position camera unit. In some embodiments, block5140 includes activating a plurality of camera units. In someembodiments, block 5140 includes activating at least one camera unitincluding activating non-visual components of the at least one cameraunit. In some embodiments, block 5140 includes activating at least onecamera unit including a microphone. In some embodiments, block 5140includes activating at least one camera unit including a RFID detector.In some embodiments, block 5140 can include activating at least onecamera unit for video data acquisition. In some embodiments, block 5140can include activating at least one camera unit for a series of dataacquisition events. In some embodiments, block 5140 includes activatingat least one camera unit for data acquisition including near-infrared(IR) data. In some embodiments, block 5140 includes activating at leastone camera unit for data acquisition including thermal data. In someembodiments, block 5140 includes activating at least one micropowerimpulse radar (MIR) device

Block 5150 illustrates identifying an end of the time intervalassociated with the first medication event. In some embodiments, block5150 includes associating a clock time interval with the end of the timeinterval associated with the first medication event. In someembodiments, block 5150 includes associating an elapsed time intervalwith the end of the time interval associated with the first medicationevent.

Block 5160 shows accepting data relating to the time interval associatedwith the first medication event from the at least one camera unit. Insome embodiments, block 5160 includes accepting data generated by the atleast one camera unit during the time interval associated with the firstmedication event. In some embodiments, block 5160 includes acceptingdata relating to the time interval associated with the first medicationevent from each of a plurality of camera units.

Block 5170 shows deactivating the at least one camera unit in responseto the identification of the end of the time interval associated withthe first medication event. In some embodiments, block 5170 includesdeactivating at least one camera unit within a mobile phone. In someembodiments, block 5170 includes deactivating at least one camera unitwithin a portable computing device. In some embodiments, block 5170includes deactivating at least one camera unit within a fixed positioncamera unit. In some embodiments, block 5170 includes deactivating aplurality of camera units.

In some embodiments, the method illustrated in FIG. 51 can includeadditional steps. For example, in some embodiments the method includesactivating an indicator in response to the circuitry for accepting datarelating to the time interval associated with the first medication eventfrom the at least one camera unit. For example, in some embodiments themethod includes saving the accepted data relating to the time intervalassociated with the first medication event from the at least one cameraunit into a memory, for example a memory within the computer system. Forexample, in some embodiments the method includes: processing theaccepted data relating to the time interval associated with the firstmedication event from the at least one camera unit into a transmission;and transmitting the processed data, for example within units of thecomputer system or to a secondary computing unit. For example, in someembodiments the method includes activating an indicator in response tothe identification of the end of the time interval associated with thefirst medication event. An indicator can be part of the computer systemor a secondary computing unit. For example, in some embodiments themethod includes: retrieving at least one attribute of the individualfrom memory; examining the accepted data for the at least one attributeof the individual; forming an identification result for the individualfrom the examination; and transmitting the identification result for theindividual. For example, in some embodiments the method includes:retrieving at least one attribute of the medication from memory;examining the accepted data for the at least one attribute of themedication; forming an identification result for the medication from theexamination; and transmitting the identification result for themedication. For example, in some embodiments the method includesinitiating a transmission in response to the identification of the startof the time interval associated with the first medication event.

In some embodiments the method includes: associating a second timeinterval with a second medication event for the individual; identifyinga start of the second time interval associated with the secondmedication event; activating an indicator in response to theidentification of the start of the second time interval associated withthe second medication event; activating at least one camera unitassociated with the individual, the activating in response to theidentification of the start of the second time interval associated withthe second medication event; identifying an end of the second timeinterval associated with the second medication event; accepting datarelating to the second time interval associated with the secondmedication event from the at least one camera unit; and deactivating theat least one camera unit in response to the identification of the end ofthe second time interval associated with the second medication event.The method can further include: comparing the time interval associatedwith the first medication event and the second time interval associatedwith the second medication event with a standard time interval; andactivating an indicator if either the time interval associated with thefirst medication event or the second time interval associated with thesecond medication event are distinct from the standard time interval.The method can further include: comparing the accepted data relating tothe time interval associated with the first medication event with a setof standard medication event parameters; comparing the accepted datarelating to the second time interval associated with the secondmedication event with a set of standard medication event parameters; andactivating an indicator if either the accepted data relating to the timeinterval associated with the first medication event or the accepted datarelating to the second time interval associated with the secondmedication event are distinct from the set of standard medication eventparameters.

FIG. 52 illustrates diagram of aspects of a system for monitoringmedication events. The system can be a computer system such as depictedin FIG. 1 and described herein. The system 5200 depicted in FIG. 52includes electrical circuitry. The circuitry of the system 5200 isconfigured to carry out a series of logical processes. As illustrated inFIG. 52, a system 5200 for monitoring medication events includes one ormore circuitry components 5210, 5220, 5230, 5240, 5250, 5260, 5270,5280, 5290, 5295. The circuitry is configured to carry out specificprocesses.

The system 5200 includes circuitry 5210 for identifying a start of atime interval associated with a first medication event for anindividual. The system 5200 includes circuitry 5220 for activating atleast one camera unit associated with the individual, the activating inresponse to the identification of the start of the time interval. Thesystem 5200 includes circuitry 5230 for accepting data from the at leastone camera unit, the data including both visual and non-visual data. Thesystem 5200 includes circuitry 5240 for providing at least onesufficiency parameter for visual data from the first medication event.The system 5200 includes circuitry 5250 for providing at least onesufficiency parameter for non-visual data from the first medicationevent. The system 5200 includes circuitry 5260 for comparing theaccepted data from the at least one camera unit with the provided atleast one sufficiency parameter for visual data and with the provided atleast one sufficiency parameter for non-visual data. The system 5200includes circuitry 5270 for determining, from the comparison, if theaccepted data from the at least one camera unit is sufficient. Thesystem 5200 includes circuitry 5280 for activating an indicator inresponse to the determined sufficiency. The system 5200 includescircuitry 5290 for identifying an end of the time interval associatedwith the first medication event. The system 5200 includes circuitry 5295for deactivating the at least one camera unit in response to theidentification of the end of the time interval associated with the firstmedication event.

FIG. 53 illustrates additional aspects of the system shown in FIG. 52.The system 5200 includes circuitry 5210 for identifying a start of atime interval associated with a first medication event for anindividual. FIG. 53 illustrates that circuitry 5210 can include one ormore of circuitry 5300 and circuitry 5310. Circuitry 5300 includescircuitry for identifying the start of a clock time interval. Circuitry5310 includes circuitry for identifying the start of an elapsed timeinterval. The system 5200 includes circuitry 5220 for activating atleast one camera unit associated with the individual, the activating inresponse to the identification of the start of the time interval. FIG.53 illustrates that circuitry 5220 can include one or more of circuitry5320 and circuitry 5330. Circuitry 5320 includes circuitry foractivating at least one camera unit within a mobile device associatedwith the individual. Circuitry 5330 includes circuitry for activatingthe at least one camera unit at a fixed location associated with theindividual.

FIG. 54 illustrates additional aspects of the system shown in FIG. 52.The system 5200 includes circuitry 5230 for accepting data from the atleast one camera unit, the data including both visual and non-visualdata. FIG. 54 illustrates that circuitry 5230 can include one or more ofcircuitry 5400, 5410, 5420, 5430, 5440, 5450, 5460. Circuitry 5400includes circuitry for accepting data including at least two visualimages. Circuitry 5410 includes circuitry for accepting data includingvideo data. Circuitry 5420 includes circuitry for accepting dataincluding near-infrared (IR) data. Circuitry 5430 includes circuitry foraccepting data including thermal data. Circuitry 5440 includes circuitryfor accepting data including audio data. Circuitry 5450 includescircuitry for accepting data including RF (radio frequency) data.Circuitry 5460 includes circuitry for accepting data includingmicropower impulse radar (MIR)-generated data.

FIG. 55 shows additional aspects of the system shown in FIG. 52. Thesystem 5200 includes circuitry 5240 for providing at least onesufficiency parameter for visual data from the first medication event.FIG. 55 illustrates that, in some embodiments, circuitry 5240 includesone or more of circuitry 5500, 5510, 5520. Circuitry 5500 includescircuitry for providing the at least one sufficiency parameter forvisual data specific to the individual. Circuitry 5510 includescircuitry for providing the at least one sufficiency parameter forvisual data including a range of values. Circuitry 5520 includescircuitry for providing the at least one sufficiency parameter forvisual data including a minimum value.

FIG. 56 shows additional aspects of the system shown in FIG. 52. Thesystem 5200 includes circuitry 5250 for providing at least onesufficiency parameter for non-visual data from the first medicationevent. FIG. 56 shows that, in some embodiments, circuitry 5250 caninclude one or more of circuitry 5600, 5610, 5620. Circuitry 5600includes circuitry for providing the at least one sufficiency parameterfor non-visual data specific to the individual. Circuitry 5610 includescircuitry for providing the at least one sufficiency parameter fornon-visual data including a range of values. Circuitry 5620 includescircuitry for providing the at least one sufficiency parameter fornon-visual data including a minimum value.

FIG. 57 depicts additional aspects of the system shown in FIG. 52. Thesystem 5200 includes circuitry 5260 for comparing the accepted data fromthe at least one camera unit with the provided at least one sufficiencyparameter for visual data and with the provided at least one sufficiencyparameter for non-visual data. FIG. 57 depicts that, in someembodiments, circuitry 5260 includes one or more of circuitry 5700,5710, 5720. Circuitry 5700 includes circuitry for comparing the accepteddata from the at least one camera unit with at least one minimum valuefor visual data and at least one minimum value for non-visual data.Circuitry 5710 includes circuitry for comparing the accepted data fromthe at least one camera unit with at least one range of values forvisual data and at least one range of values for non-visual data.Circuitry 5720 includes circuitry for comparing the accepted data fromthe at least one camera unit with at least one sufficiency parameter forvisual data specific to the individual and at least one sufficiencyparameter for non-visual data specific to the individual.

FIG. 57 depicts additional aspects of the system shown in FIG. 52. Thesystem 5200 includes circuitry 5270 for determining, from thecomparison, if the accepted data from the at least one camera unit issufficient. In some embodiments, circuitry 5270 includes circuitry 5800.Circuitry 5800 includes circuitry for determining that the accepted datafrom the at least one camera unit is insufficient. As illustrated inFIG. 57, the system 5200 includes circuitry 5280 for activating anindicator in response to the determined sufficiency. In someembodiments, circuitry 5280 includes one or more of circuitry 5810,5820. Circuitry 5810 includes circuitry for activating a visualindicator. Circuitry 5820 includes circuitry for activating an audioindicator. As shown in FIG. 57, the system 5200 includes circuitry 5290for identifying an end of the time interval associated with the firstmedication event. In some embodiments, circuitry 5290 includes one ormore of circuitry 5830, 5840. Circuitry 5830 includes circuitry foridentifying the end of a clock time interval. Circuitry 5840 includescircuitry for identifying the end of an elapsed time interval.

FIG. 59 shows additional aspects of the system shown in FIG. 52. Thesystem 5200 includes circuitry 5295 for deactivating the at least onecamera unit in response to the identification of the end of the timeinterval associated with the first medication event. In someembodiments, circuitry 5295 includes one or more of circuitry 5900,5910. Circuitry 5900 includes circuitry for deactivating at least onecamera unit within a mobile device associated with the individual.Circuitry 5910 includes circuitry for deactivating at least one cameraunit at a fixed location associated with the individual. FIG. 59 alsoillustrates that, in some embodiments, the system 5200 can include oneor more of circuitry 5920, 5930. Circuitry 5920 includes circuitry forsaving the accepted data from the at least one camera unit in a memory.Circuitry 5930 includes: circuitry for processing the accepted data fromthe at least one camera unit; and circuitry for transmitting theprocessed data.

FIG. 60 illustrates additional aspects of the system depicted in FIG.52. FIG. 60 shows that, in some embodiments, the system can include oneor more of circuitry 6000, 6010, 6020, 6030, 6040. Circuitry 6000includes circuitry for saving the determined sufficiency in a memory.Circuitry 6010 includes circuitry for transmitting the determinedsufficiency. Circuitry 6020 includes circuitry for identifying, inresponse to the determined sufficiency, a start of a time intervalassociated with a supplementary medication event for the individual.Circuitry 6030 includes circuitry for activating an indicator inresponse to the identification of the start of the time intervalassociated with the first medication event. Circuitry 6040 includescircuitry for deactivating an indicator in response to theidentification of the end of the time interval associated with the firstmedication event.

FIG. 61 shows additional aspects of the system depicted in FIG. 52. FIG.61 shows that, in some embodiments, the system can include one or moreof circuitry 6100, 6110. Circuitry 6100 includes: circuitry forprocessing the accepted data from the at least one camera unit into amedication record for the individual; and circuitry for transmitting themedication record. Circuitry 6110 includes circuitry for activating anindicator in response to the identification of the end of the timeinterval associated with the first medication event.

FIG. 62 depicts additional aspects of the system shown in FIG. 52. FIG.62 shows that, in some embodiments, system 5200 for monitoringmedication events can include circuitry 6200, and can also includecircuitry 6210. As illustrated in FIG. 52, a system 5200 for monitoringmedication events includes one or more circuitry components 5210, 5220,5230, 5240, 5250, 5260, 5270, 5280, 5290, 5295. Although circuitry 5210,5220, 5230, 5240, 5250, 5260, 5270, 5280, 5290, 5295 are not depicted inFIG. 62 to improve clarity, the system 5200 should be understood toinclude those components. Circuitry 6200 includes: circuitry foridentifying a start of a second time interval associated with a secondmedication event for the individual; circuitry for activating the atleast one camera unit associated with the individual, the activating inresponse to the identification of the start of the second time interval;circuitry for accepting data from the at least one camera unit, the dataincluding both visual and non-visual data; circuitry for providing theat least one sufficiency parameter for visual data from the secondmedication event; circuitry for providing the at least one sufficiencyparameter for non-visual data from the second medication event;circuitry for comparing the accepted data from the at least one cameraunit with the provided at least one sufficiency parameter for visualdata and with the provided at least one sufficiency parameter fornon-visual data; circuitry for determining, from the comparison, if theaccepted data from the at least one camera unit is sufficient; circuitryfor activating an indicator in response to the determined sufficiency;circuitry for identifying an end of the second time interval associatedwith the second medication event; and circuitry for deactivating the atleast one camera unit in response to the identification of the end ofthe time interval associated with the second medication event. In someembodiments, circuitry 6200 can include circuitry 6210. Circuitry 6210includes circuitry for identifying, in response to the determinedsufficiency of the second medication event, a start of a time intervalassociated with a supplementary medication event for the individual.

FIG. 63 shows aspects of a computer system 120 including at least onemain computing unit 125. Although a single main computing unit 125 isillustrated in FIG. 63, in some embodiments there may be a plurality ofmain computing units 125. A main computing unit 125 includescomputer-readable storage medium including executable instructions formonitoring medication events 6300. The computer-readable storage mediumincluding executable instructions for monitoring medication events 6300includes instructions 6310, 6320, 6330, 6340, 6350, 6360, 6370, 6380,6390, 6395. Instructions 6310 include instructions for identifying astart of a time interval associated with a first medication event for anindividual. Instructions 6320 include instructions for activating atleast one camera unit associated with the individual, the activating inresponse to the identification of the start of the time interval.Instructions 6330 include instructions for accepting data from the atleast one camera unit, the data including both visual and non-visualdata. Instructions 6340 include instructions for providing at least onesufficiency parameter for visual data from the first medication event.Instructions 6350 include instructions for providing at least onesufficiency parameter for non-visual data from the first medicationevent. Instructions 6360 include instructions for comparing the accepteddata from the at least one camera unit with the provided at least onesufficiency parameter for visual data and with the provided at least onesufficiency parameter for non-visual data. Instructions 6370 includeinstructions for determining, from the comparison, if the accepted datafrom the at least one camera unit is sufficient. Instructions 6380include instructions for activating an indicator in response to thedetermined sufficiency. Instructions 6390 include instructions foridentifying an end of the time interval associated with the firstmedication event. Instructions 6395 include instructions fordeactivating the at least one camera unit in response to theidentification of the end of the time interval associated with the firstmedication event.

Instructions 6310 include instructions for identifying a start of a timeinterval associated with a first medication event for an individual. Insome embodiments, instructions 6310 include additional instructions. Forexample, in some embodiments, instructions 6310 include instructions foridentifying the start of a clock time interval. For example, in someembodiments, instructions 6310 include instructions for identifying thestart of an elapsed time interval.

Instructions 6320 include instructions for activating at least onecamera unit associated with the individual, the activating in responseto the identification of the start of the time interval. In someembodiments, instructions 6320 include additional instructions. Forexample, in some embodiments, instructions 6320 include instructions foractivating at least one camera unit within a mobile device associatedwith the individual. For example, in some embodiments, instructions 6320include instructions for activating the at least one camera unit at afixed location associated with the individual.

Instructions 6330 include instructions for accepting data from the atleast one camera unit, the data including both visual and non-visualdata. In some embodiments, instructions 6330 include additionalinstructions. For example, in some embodiments, instructions 6330include instructions for accepting data including at least two visualimages. For example, in some embodiments, instructions 6330 includeinstructions for accepting data including video data. For example, insome embodiments, instructions 6330 include instructions for acceptingdata including near-infrared (IR) data. For example, in someembodiments, instructions 6330 include instructions for accepting dataincluding thermal data. For example, in some embodiments, instructions6330 include instructions for accepting data including audio data. Forexample, in some embodiments, instructions 6330 include instructions foraccepting data including RF (radio frequency) data. For example, in someembodiments, instructions 6330 include instructions for accepting dataincluding micropower impulse radar (MIR)-generated data.

Instructions 6340 include instructions for providing at least onesufficiency parameter for visual data from the first medication event.In some embodiments, instructions 6340 include additional instructions.For example, in some embodiments, instructions 6340 include instructionsfor providing at least one sufficiency parameter for visual dataspecific to the individual. For example, in some embodiments,instructions 6340 include instructions for providing at least onesufficiency parameter for visual data including a range of values. Forexample, in some embodiments, instructions 6340 include instructions forproviding at least one sufficiency parameter for visual data including aminimum value.

Instructions 6350 include instructions for providing at least onesufficiency parameter for non-visual data from the first medicationevent. In some embodiments, instructions 6350 include additionalinstructions. For example, in some embodiments, instructions 6350include instructions for providing at least one sufficiency parameterfor non-visual data specific to the individual. For example, in someembodiments, instructions 6350 include instructions for providing atleast one sufficiency parameter for non-visual data including a range ofvalues. For example, in some embodiments, instructions 6350 includeinstructions for providing at least one sufficiency parameter fornon-visual data including a minimum value.

Instructions 6360 include instructions for comparing the accepted datafrom the at least one camera unit with the provided at least onesufficiency parameter for visual data and with the provided at least onesufficiency parameter for non-visual data. In some embodiments,instructions 6360 include additional instructions. For example, in someembodiments, instructions 6360 include instructions for comparing theaccepted data from the at least one camera unit with at least oneminimum value for visual data and at least one minimum value fornon-visual data. For example, in some embodiments, instructions 6360include instructions for comparing the accepted data from the at leastone camera unit with at least one range of values for visual data and atleast one range of values for non-visual data. For example, in someembodiments, instructions 6360 include instructions for comparing theaccepted data from the at least one camera unit with at least onesufficiency parameter for visual data specific to the individual and atleast one sufficiency parameter for non-visual data specific to theindividual.

Instructions 6370 include instructions for determining, from thecomparison, if the accepted data from the at least one camera unit issufficient. In some embodiments, instructions 6370 include additionalinstructions. For example, in some embodiments, instructions 6370include instructions for determining that the accepted data from the atleast one camera unit is insufficient.

Instructions 6380 include instructions for activating an indicator inresponse to the determined sufficiency. In some embodiments,instructions 6380 include additional instructions. For example, in someembodiments, instructions 6380 include instructions for activating avisual indicator. For example, in some embodiments, instructions 6380include instructions for activating an audio indicator.

Instructions 6390 include instructions for identifying an end of thetime interval associated with the first medication event. In someembodiments, instructions 6390 include additional instructions. Forexample, in some embodiments, instructions 6390 include instructions foridentifying the end of a clock time interval. For example, in someembodiments, instructions 6380 include instructions for identifying theend of an elapsed time interval.

Instructions 6395 include instructions for deactivating the at least onecamera unit in response to the identification of the end of the timeinterval associated with the first medication event. In someembodiments, instructions 6395 include additional instructions. Forexample, in some embodiments, instructions 6395 include instructions fordeactivating at least one camera unit within a mobile device associatedwith the individual. For example, in some embodiments, instructions 6395include instructions for deactivating at least one camera unit at afixed location associated with the individual.

As illustrated in FIG. 63, a computer-readable storage medium includingexecutable instructions for monitoring medication events 6300 includesinstructions 6310, 6320, 6330, 6340, 6350, 6360, 6370, 6380, 6390, 6395.In some embodiments, the executable instructions for monitoringmedication events 6300 illustrated in FIG. 63 includes additional setsof instructions. In some embodiments, the computer-readable storagemedium including executable instructions for monitoring medicationevents 6300 includes instructions for saving the accepted data from theat least one camera unit in a memory. In some embodiments, thecomputer-readable storage medium including executable instructions formonitoring medication events 6300 includes: instructions for processingthe accepted data from the at least one camera unit; and instructionsfor transmitting the processed data. In some embodiments, thecomputer-readable storage medium including executable instructions formonitoring medication events 6300 includes instructions for saving thedetermined sufficiency in a memory. In some embodiments, thecomputer-readable storage medium including executable instructions formonitoring medication events 6300 includes instructions for transmittingthe determined sufficiency. In some embodiments, the computer-readablestorage medium including executable instructions for monitoringmedication events 6300 includes instructions for identifying, inresponse to the determined sufficiency, a start of a time intervalassociated with a supplementary medication event for the individual. Insome embodiments, the computer-readable storage medium includingexecutable instructions for monitoring medication events 6300 includesinstructions for activating an indicator in response to theidentification of the start of the time interval associated with thefirst medication event. In some embodiments, the computer-readablestorage medium including executable instructions for monitoringmedication events 6300 includes instructions for deactivating anindicator in response to the identification of the end of the timeinterval associated with the first medication event. In someembodiments, the computer-readable storage medium including executableinstructions for monitoring medication events 6300 includes instructionsfor activating an indicator in response to the identification of the endof the time interval associated with the first medication event. In someembodiments, the computer-readable storage medium including executableinstructions for monitoring medication events 6300 includes:instructions for processing the accepted data from the at least onecamera unit into a medication record for the individual; andinstructions for transmitting the medication record. In someembodiments, the computer-readable storage medium including executableinstructions for monitoring medication events 6300 includes:instructions for identifying a start of a second time intervalassociated with a second medication event for the individual;instructions for activating the at least one camera unit associated withthe individual, the activating in response to the identification of thestart of the second time interval; instructions for accepting data fromthe at least one camera unit, the data including both visual andnon-visual data; instructions for providing the at least one sufficiencyparameter for visual data from the second medication event; instructionsfor providing the at least one sufficiency parameter for non-visual datafrom the second medication event; instructions for comparing theaccepted data from the at least one camera unit with the provided atleast one sufficiency parameter for visual data and with the provided atleast one sufficiency parameter for non-visual data; instructions fordetermining, from the comparison, if the accepted data from the at leastone camera unit is sufficient; instructions for activating an indicatorin response to the determined sufficiency; instructions for identifyingan end of the second time interval associated with the second medicationevent; and instructions for deactivating the at least one camera unit inresponse to the identification of the end of the time intervalassociated with the second medication event. In some embodiments, thecomputer-readable storage medium including executable instructions formonitoring medication events 6300 includes instructions for identifying,in response to the determined sufficiency of the second medicationevent, a start of a time interval associated with a supplementarymedication event for the individual.

FIG. 64 illustrates a flowchart of a method 6400 for monitoringmedication events. These method steps can be carried out, for example,by a computer system (e.g. item 120 in FIG. 1). FIG. 64 shows that themethod includes a series of steps, 6410, 6420, 6430, 6440, 6450, 6460,6470, 6480, 6490, 6495. Method step 6410 includes identifying a start ofa time interval associated with a first medication event for anindividual. Method step 6420 includes activating at least one cameraunit associated with the individual, the activating in response to theidentification of the start of the time interval. Method step 6430includes accepting data from the at least one camera unit, the dataincluding both visual and non-visual data. Method step 6440 includesproviding at least one sufficiency parameter for visual data from thefirst medication event. Method step 6450 includes providing at least onesufficiency parameter for non-visual data from the first medicationevent. Method step 6460 includes comparing the accepted data from the atleast one camera unit with the provided at least one sufficiencyparameter for visual data and with the provided at least one sufficiencyparameter for non-visual data. Method step 6470 includes determining,from the comparison, if the accepted data from the at least one cameraunit is sufficient. Method step 6480 includes activating an indicator inresponse to the determined sufficiency. Method step 6490 includesidentifying an end of the time interval associated with the firstmedication event. Method step 6495 includes deactivating the at leastone camera unit in response to the identification of the end of the timeinterval associated with the first medication event.

In some embodiments, the flowchart of the method illustrated in FIG. 64can be shown with further details. For example, method step 6410includes identifying a start of a time interval associated with a firstmedication event for an individual. In some embodiments, method step6410 can include identifying the start of a clock time interval. In someembodiments, method step 6410 can include identifying the start of anelapsed time interval.

Method step 6420 includes activating at least one camera unit associatedwith the individual, the activating in response to the identification ofthe start of the time interval. In some embodiments, method step 6420can include activating at least one camera unit within a mobile deviceassociated with the individual. In some embodiments, method step 6420can include activating at least one camera unit at a fixed locationassociated with the individual.

Method step 6430 includes accepting data from the at least one cameraunit, the data including both visual and non-visual data. In someembodiments, method step 6430 can include accepting data including atleast two visual images. In some embodiments, method step 6430 caninclude accepting data including video data. In some embodiments, methodstep 6430 can include accepting data including near-infrared (IR) data.In some embodiments, method step 6430 can include accepting dataincluding thermal data. In some embodiments, method step 6430 caninclude accepting data including audio data. In some embodiments, methodstep 6430 can include accepting data including RF (radio frequency)data. In some embodiments, method step 6430 can include accepting dataincluding micropower impulse radar (MIR)-generated data.

Method step 6440 includes providing at least one sufficiency parameterfor visual data from the first medication event. In some embodiments,method step 6440 can include providing at least one sufficiencyparameter for visual data specific to the individual. In someembodiments, method step 6440 can include providing at least onesufficiency parameter for visual data including a range of values. Insome embodiments, method step 6440 can include providing at least onesufficiency parameter for visual data including a minimum value.

Method step 6450 includes providing at least one sufficiency parameterfor visual data from the first medication event. In some embodiments,method step 6450 can include providing at least one sufficiencyparameter for non-visual data specific to the individual. In someembodiments, method step 6450 can include providing at least onesufficiency parameter for non-visual data including a range of values.In some embodiments, method step 6450 can include providing at least onesufficiency parameter for non-visual data including a minimum value.

Method step 6460 includes comparing the accepted data from the at leastone camera unit with the provided at least one sufficiency parameter forvisual data and with the provided at least one sufficiency parameter fornon-visual data. In some embodiments, method step 6460 can includecomparing the accepted data from the at least one camera unit with atleast one minimum value for visual data and at least one minimum valuefor non-visual data. In some embodiments, method step 6460 can includecomparing the accepted data from the at least one camera unit with atleast one range of values for visual data and at least one range ofvalues for non-visual data. In some embodiments, method step 64560 caninclude comparing the accepted data from the at least one camera unitwith at least one sufficiency parameter for visual data specific to theindividual and at least one sufficiency parameter for non-visual dataspecific to the individual.

Method step 6470 includes determining, from the comparison, if theaccepted data from the at least one camera unit is sufficient. In someembodiments, method step 6470 can include determining that the accepteddata from the at least one camera unit is insufficient.

Method step 6480 includes activating an indicator in response to thedetermined sufficiency. In some embodiments, method step 6480 caninclude activating a visual indicator. In some embodiments, method step6480 can include activating an audio indicator.

Method step 6490 includes identifying an end of the time intervalassociated with the first medication event. In some embodiments, methodstep 6490 can include identifying the end of a clock time interval. Insome embodiments, method step 6490 can include identifying the end of anelapsed time interval.

Method step 6495 includes deactivating the at least one camera unit inresponse to the identification of the end of the time intervalassociated with the first medication event. In some embodiments, methodstep 6495 can include deactivating at least one camera unit within amobile device associated with the individual. In some embodiments,method step 6495 can include deactivating at least one camera unit at afixed location associated with the individual.

In some embodiments, the flowchart illustrated in FIG. 64 can includeadditional steps. For example, the method can include saving theaccepted data from the at least one camera unit in a memory. Forexample, the method can include: processing the accepted data from theat least one camera unit; and transmitting the processed data. Forexample, the method can include saving the determined sufficiency in amemory. For example, the method can include transmitting the determinedsufficiency. For example, the method can include identifying, inresponse to the determined sufficiency, a start of a time intervalassociated with a supplementary medication event for the individual. Forexample, the method can include activating an indicator in response tothe identification of the start of the time interval associated with thefirst medication event. For example, the method can include deactivatingan indicator in response to the identification of the end of the timeinterval associated with the first medication event. For example, themethod can include activating an indicator in response to theidentification of the end of the time interval associated with the firstmedication event. For example, the method can include: processing theaccepted data from the at least one camera unit into a medication recordfor the individual; and transmitting the medication record.

In some embodiments, the flowchart shown in FIG. 64 can includeadditional steps. For example, the method can include: identifying astart of a second time interval associated with a second medicationevent for the individual; activating the at least one camera unitassociated with the individual, the activating in response to theidentification of the start of the second time interval; accepting datafrom the at least one camera unit, the data including both visual andnon-visual data; providing the at least one sufficiency parameter forvisual data from the second medication event; providing the at least onesufficiency parameter for non-visual data from the second medicationevent; comparing the accepted data from the at least one camera unitwith the provided at least one sufficiency parameter for visual data andwith the provided at least one sufficiency parameter for non-visualdata; determining, from the comparison, if the accepted data from the atleast one camera unit is sufficient; activating an indicator in responseto the determined sufficiency; identifying an end of the second timeinterval associated with the second medication event; and deactivatingthe at least one camera unit in response to the identification of theend of the time interval associated with the second medication event.This method can also include: identifying, in response to the determinedsufficiency of the second medication event, a start of a time intervalassociated with a supplementary medication event for the individual.

FIG. 65 illustrates further aspects of the systems and methods describedherein. FIG. 65 illustrates diagram of aspects of a system formonitoring medication events. The system can be a computer system suchas depicted in FIG. 1 and described herein. The system 6500 depicted inFIG. 65 includes electrical circuitry. The circuitry of the system 6500is configured to carry out a series of logical processes. As illustratedin FIG. 65, a system 6500 for monitoring medication events relating toan individual includes one or more circuitry components 6510, 6520,6530, 6540, 6550, 6560, 6570, 6580, 6590, 6595. The circuitry isconfigured to carry out specific processes.

The system 6500 includes circuitry 6510 for accepting first data from acamera unit associated with an individual. The system 6500 includescircuitry 6520 for providing a set of medication intervention parametersfor the individual. The system 6500 includes circuitry 6530 forcomparing the accepted first data from the camera unit associated withthe individual with the provided set of medication interventionparameters for the individual. The system 6500 includes circuitry 6540for determining if the accepted first data is within the provided set ofmedication intervention parameters. The system 6500 includes circuitry6550 for activating at least one indicator in response to the firstdetermination. The system 6500 includes circuitry 6560 for acceptingsecond data from the camera unit associated with the individual, thesecond data obtained after the activation of the at least one indicator.The system 6500 includes circuitry 6570 for analyzing the acceptedsecond data for at least one attribute relating to the medication event.The system 6500 includes circuitry 6580 for comparing the acceptedsecond data with the provided set of medication intervention parametersfor the individual. The system 6500 includes circuitry 6590 fordetermining if the accepted second data is within the provided set ofmedication intervention parameters. The system 6500 includes circuitry6595 for activating the at least one indicator in response to the seconddetermination.

FIG. 66 illustrates other aspects of the system 6500 depicted in FIG.65. As shown in FIG. 66, in some embodiments the circuitry 6510 foraccepting first data from a camera unit associated with an individualincludes additional aspects. FIG. 66 illustrates that in someembodiments, circuitry 6510 can include one or more of circuitry 6600,6610, 6620, 6630, 6640, 6650. Circuitry 6600 includes circuitry foraccepting visual data and accepting non-visual data. Circuitry 6610includes circuitry for accepting data from a camera unit integral to amobile device. Circuitry 6620 includes circuitry for accepting data froma camera unit integral to a fixed-location device. Circuitry 6630includes circuitry for accepting data including at least two visualimages. Circuitry 6640 includes circuitry for accepting data includingvideo data. Circuitry 6650 includes circuitry for accepting dataincluding near-infrared (IR) data.

FIG. 67 illustrates further aspects of the circuitry depicted in FIG.65. FIG. 67 illustrates that, in some embodiments, circuitry 6510 foraccepting first data from a camera unit associated with an individualincludes additional aspects. FIG. 67 illustrates that in someembodiments, circuitry 6510 can include one or more of circuitry 6700,6710, 6720, 6730. Circuitry 6700 includes circuitry for accepting dataincluding radio frequency (RF) data. Circuitry 6710 includes circuitryfor accepting data including data from a micropower impulse radar (MIR)device.

FIG. 67 also shows that, in some embodiments, the circuitry 6520 of FIG.65 can also include one or more of circuitry 6740, 6750. The system 6500includes circuitry 6520 for providing a set of medication interventionparameters for the individual. Circuitry 6720 includes circuitry foraccepting data including thermal data. Circuitry 6730 includes circuitryfor accepting data including audio data.

FIG. 68 depicts further aspects of the circuitry depicted in FIG. 65.FIG. 68 illustrates that, in some embodiments, circuitry 6520 forproviding a set of medication intervention parameters for the individualincludes additional aspects. FIG. 68 illustrates that in someembodiments, circuitry 6520 can include one or more of circuitry 6800,6810, 6820, 6830. Circuitry 6800 includes providing the set ofmedication intervention parameters for the individual including audioparameters. Circuitry 6810 includes circuitry for providing the set ofmedication intervention parameters for the individual includingnear-infrared (IR) parameters. Circuitry 6820 includes circuitry forproviding the set of medication intervention parameters for theindividual including thermal parameters. Circuitry 6830 includescircuitry for providing the set of medication intervention parametersfor the individual including micropower impulse radar parameters.

FIG. 69 shows aspects of the circuitry illustrated in FIG. 65. FIG. 69illustrates that, in some embodiments, circuitry 6530 for comparing theaccepted first data from the camera unit associated with the individualwith the provided set of medication intervention parameters for theindividual can include one or more of circuitry 6900, 6910, 6920, 6930.Circuitry 6900 includes circuitry for comparing the accepted first datawith at least one minimum sufficiency parameter. Circuitry 6910 includescircuitry for comparing the accepted first data with a set of parametersassociated with the individual. Circuitry 6920 includes circuitry forcomparing the accepted first data with a range of sufficiencyparameters. Circuitry 6930 includes circuitry for comparing the acceptedfirst data with a series of minimum medication intervention parameters.

FIG. 70 shows aspects of the system 6500 illustrated in FIG. 65. FIG. 70depicts that, in some embodiments, circuitry 6540 for determining if theaccepted first data is within the provided set of medicationintervention parameters can include circuitry 7000. Circuitry 7000includes circuitry for determining that the accepted first data eitheris within the provided set of medication intervention parameters or isnot within the provided set of medication intervention parameters. FIG.70 also depicts that, in some embodiments, circuitry 6550 for activatingat least one indicator in response to the first determination caninclude one or more of circuitry 7010, 7020, or 7030. Circuitry 7010includes circuitry for activating a visual indicator. Circuitry 7020includes circuitry for activating an audio indicator. Circuitry 7030includes circuitry for activating a vibratory indicator.

FIG. 71 depicts aspects of the system 6500 illustrated in FIG. 65. FIG.71 shows that, in some embodiments, circuitry 6560 for accepting seconddata from the camera unit associated with the individual, the seconddata obtained after the activation of the at least one indicator caninclude one or more of circuitry 7100, 7110. Circuitry 7100 includescircuitry for accepting second data from at least one camera unit, thesecond data including at least one time value. Circuitry 7110 includescircuitry for accepting data including visual data, non-visual data, andat least one time value. FIG. 71 also shows that, in some embodiments,circuitry 6570 for analyzing the accepted second data for at least oneattribute relating to the medication event can include circuitry 7120.Circuitry 7120 includes: circuitry for presenting at least one attributerelating to a medication event; and circuitry for analyzing the acceptedsecond data for the at least one attribute relating to a medicationevent.

FIG. 72 shows aspects of the system 6500 illustrated in FIG. 65. FIG. 72depicts that, in some embodiments, circuitry 6570 for analyzing theaccepted second data for at least one attribute relating to themedication event can include one or more of circuitry 7200, 7210.Circuitry 7200 includes circuitry for analyzing the accepted second datafor at least one visual attribute. Circuitry 7210 includes circuitry foranalyzing the accepted second data for at least one non-visualattribute. FIG. 72 also depicts that, in some embodiments, circuitry6580 for comparing the accepted second data with the provided set ofmedication intervention parameters for the individual includes circuitry7220. Circuitry 7220 includes circuitry for comparing both visual dataand non-visual data.

FIG. 73 shows that the system 6500 illustrated in FIG. 65 can alsoinclude circuitry 7300, 7310, 7320, 7330. FIG. 73 shows that, in someembodiments, circuitry 6590 for determining if the accepted second datais within the provided set of medication intervention parameters caninclude circuitry 7300. Circuitry 7300 includes circuitry fordetermining that the accepted second data either is within the providedset of medication intervention parameters or is not within the providedset of medication intervention parameters. FIG. 73 shows that, in someembodiments, circuitry 6595 for activating the at least one indicator inresponse to the second determination can include one or more ofcircuitry 7310, 7320, 7330. Circuitry 73010 includes circuitry foractivating at least one visual indicator. Circuitry 7320 includescircuitry for activating at least one audio indicator. Circuitry 7330includes circuitry for activating at least one vibratory indicator.

FIG. 74 shows additional aspects of the system 6500 shown in FIG. 65.FIG. 74 depicts that, in some embodiments, system 6500 can include oneor more of circuitry 7400, 7410, 7420, 7430. Circuitry 7400 includes:circuitry for presenting at least one attribute of the individual; andcircuitry for analyzing the accepted first data for the at least oneattribute of the individual. Circuitry 7410 includes: circuitry forpresenting at least one attribute of the individual; and circuitry foranalyzing the accepted second data for the at least one attribute of theindividual. Circuitry 7420 includes circuitry for saving the acceptedfirst data in a memory. Circuitry 7430 includes circuitry for saving theaccepted second data in a memory.

FIG. 75 depicts additional aspects of the system 6500 shown in FIG. 65.FIG. 75 illustrates that, in some embodiments, system 6500 can includeone or more of circuitry 7500, 7510. Circuitry 7500 includes: circuitryfor processing the at least one accepted first data; circuitry forprocessing the at least one accepted second data; circuitry forintegrating the processed at least one accepted first data and theprocessed at least one accepted second data into a medication record;and circuitry for saving the medication record in a memory. Circuitry7510 includes: circuitry for processing the determination if theaccepted first data is within the provided set of medicationintervention parameters into a first result; and circuitry fortransmitting the first result.

FIG. 76 illustrates additional aspects of the system 6500 shown in FIG.65. FIG. 76 shows that, in some embodiments, system 6500 can includecircuitry 7600. Circuitry 7600 includes: circuitry for processing thedetermination if the accepted second data is within the provided set ofmedication intervention parameters into a second result; and circuitryfor transmitting the second result.

FIG. 77 depicts additional aspects of the system 6500 shown in FIG. 65.FIG. 77 illustrates that, in some embodiments, system 6500 can includecircuitry 7710. Circuitry 7710 includes: circuitry for accepting thirddata from the camera unit associated with the individual, the third dataobtained after the activation of the at least one indicator in responseto the second determination; circuitry for analyzing the accepted thirddata for the at least one attribute relating to the medication event;circuitry for comparing the accepted third data with the provided set ofmedication intervention parameters for the individual; circuitry fordetermining if the accepted third data is within the provided set ofmedication intervention parameters; and circuitry for activating the atleast one indicator in response to the third determination.

FIG. 78 shows aspects of a computer system 120 including at least onemain computing unit 125. Although a single main computing unit 125 isillustrated in FIG. 78, in some embodiments there may be a plurality ofmain computing units 125. A main computing unit 125 includescomputer-readable storage medium including executable instructions formonitoring medication events 7800. The computer-readable storage mediumincluding executable instructions for monitoring medication events 7800includes instructions 7810, 7820, 7830, 7840, 7850, 7860, 7870, 7880,7890, 7895. Instructions 7810 include instructions for accepting firstdata from a camera unit associated with an individual. Instructions 7820include instructions for providing a set of medication interventionparameters for the individual. Instructions 7830 include instructionsfor comparing the accepted first data from the camera unit associatedwith the individual with the provided set of medication interventionparameters for the individual. Instructions 7840 include instructionsfor determining if the accepted first data is within the provided set ofmedication intervention parameters. Instructions 7850 includeinstructions for activating at least one indicator in response to thefirst determination. Instructions 7860 include instructions foraccepting second data from the camera unit associated with theindividual, the second data obtained after the activation of the atleast one indicator. Instructions 7870 include instructions foranalyzing the accepted second data for at least one attribute relatingto the medication event. Instructions 7880 include instructions forcomparing the accepted second data with the provided set of medicationintervention parameters for the individual. Instructions 7890 includeinstructions for determining if the accepted second data is within theprovided set of medication intervention parameters. Instructions 7895include instructions for activating the at least one indicator inresponse to the second determination.

Some embodiments include a computer-readable storage medium includingexecutable instructions for monitoring medication events 7800 includingadditional aspects. In some embodiments, instructions 7810 for acceptingfirst data from a camera unit associated with an individual include oneor more additional instructions. For example, instructions 7810 caninclude instructions for accepting visual data and accepting non-visualdata. Instructions 7810 can also include instructions for accepting datafrom a camera unit integral to a mobile device. Instructions 7810 caninclude instructions for accepting data from a camera unit integral to afixed-location device. Instructions 7810 can include instructions foraccepting data including at least two visual images. Instructions 7810can include instructions for accepting data including video data.Instructions 7810 can include instructions for accepting data includingnear-infrared (IR) data. Instructions 7810 can include instructions foraccepting data including radio frequency (RF) data. Instructions 7810can include instructions for accepting data including data from amicropower impulse radar (MIR) device. Instructions 7810 can includeinstructions for accepting data including thermal data. Instructions7810 can include instructions for accepting data including audio data.

In some embodiments, instructions 7820 for providing a set of medicationintervention parameters for the individual include one or moreadditional instructions. For example, instructions 7820 can includeinstructions for providing the set of medication intervention parametersfor the individual including time parameters. Instructions 7820 caninclude instructions for providing the set of medication interventionparameters for the individual including visual parameters. Instructions7820 can include instructions for providing the set of medicationintervention parameters for the individual including audio parameters.Instructions 7820 can include instructions for providing the set ofmedication intervention parameters for the individual includingnear-infrared (IR) parameters. Instructions 7820 can includeinstructions for providing the set of medication intervention parametersfor the individual including thermal parameters. Instructions 7820 caninclude instructions for providing the set of medication interventionparameters for the individual including micropower impulse radarparameters.

In some embodiments, instructions 7830 for comparing the accepted firstdata from the camera unit associated with the individual with theprovided set of medication intervention parameters for the individualcan include one or more additional instructions. For example, in someembodiments instructions 7830 can include instructions for comparing theaccepted first data with at least one minimum sufficiency parameter. Forexample, in some embodiments instructions 7830 can include instructionsfor comparing the accepted first data with a set of parametersassociated with the individual. For example, in some embodimentsinstructions 7830 can include instructions for comparing the acceptedfirst data with a range of sufficiency parameters. For example, in someembodiments instructions 7830 can include instructions for comparing theaccepted first data with a series of minimum medication interventionparameters.

In some embodiments, instructions 7840 for determining if the acceptedfirst data is within the provided set of medication interventionparameters can include one or more additional instructions. For example,in some embodiments instructions 7840 can include instructions fordetermining that the accepted first data either is within the providedset of medication intervention parameters or is not within the providedset of medication intervention parameters.

In some embodiments, instructions 7850 for activating at least oneindicator in response to the first determination can include one or moreadditional instructions. For example, in some embodiments instructions7850 can include instructions for activating a visual indicator. In someembodiments, instructions 7850 can include instructions for activatingan audio indicator. In some embodiments, instructions 7850 can includeinstructions for activating a vibratory indicator.

In some embodiments, instructions 7860 include instructions foraccepting second data from the camera unit associated with theindividual, the second data obtained after the activation of the atleast one indicator can include one or more additional instructions. Forexample, in some embodiments instructions 7860 can include instructionsfor accepting second data from the at least one camera unit, the seconddata including at least one time value. In some embodiments,instructions 7860 can include instructions for accepting data includingvisual data, non-visual data, and at least one time value.

In some embodiments, instructions 7870 for analyzing the accepted seconddata for at least one attribute relating to the medication event caninclude one or more additional instructions. For example, in someembodiments instructions 7870 can include: instructions for presentingat least one attribute relating to the medication event; andinstructions for analyzing the accepted second data for the at least oneattribute relating to the medication event. In some embodiments,instructions 7870 can include instructions for analyzing the acceptedsecond data for at least one visual attribute. In some embodiments,instructions 7870 can include instructions for analyzing the acceptedsecond data for at least one non-visual attribute.

In some embodiments, instructions 7880 for comparing the accepted seconddata with the provided set of medication intervention parameters for theindividual can include can include one or more additional instructions.For example, in some embodiments instructions 7880 can includeinstructions for comparing both visual data and non-visual data.

In some embodiments, instructions 7890 for determining if the acceptedsecond data is within the provided set of medication interventionparameters can include one or more additional instructions. For example,in some embodiments instructions 7890 can include instructions fordetermining that the accepted second data either is within the providedset of medication intervention parameters or is not within the providedset of medication intervention parameters.

In some embodiments, instructions 7895 for activating the at least oneindicator in response to the second determination includes one or moreadditional sets of instructions. For example, the instructions 7895 caninclude instructions for activating at least one audio indicator. Forexample, the instructions 7895 can include instructions for activatingat least one vibratory indicator.

In some embodiments, the computer-readable storage medium includingexecutable instructions for monitoring medication events 7800 includesone or more sets of additional instructions. For example, thecomputer-readable storage medium including executable instructions formonitoring medication events 7800 can include instructions including:instructions for presenting at least one attribute of the individual;and instructions for analyzing the accepted first data for the at leastone attribute of the individual. For example, the computer-readablestorage medium including executable instructions for monitoringmedication events 7800 can include instructions including: instructionsfor presenting at least one attribute of the individual; andinstructions for analyzing the accepted second data for the at least oneattribute of the individual. For example, the computer-readable storagemedium including executable instructions for monitoring medicationevents 7800 can include instructions including: instructions for savingthe accepted first data in a memory. For example, the computer-readablestorage medium including executable instructions for monitoringmedication events 7800 can include instructions including: instructionsfor saving the accepted second data in a memory. For example, thecomputer-readable storage medium including executable instructions formonitoring medication events 7800 can include instructions including:instructions for processing the at least one accepted first data;instructions for processing the at least one accepted second data;instructions for integrating the processed at least one accepted firstdata and the processed at least one accepted second data into amedication record; and instructions for saving the medication record ina memory. For example, the computer-readable storage medium includingexecutable instructions for monitoring medication events 7800 caninclude instructions including: instructions for processing thedetermination if the accepted first data is within the provided set ofmedication intervention parameters into a first result; and instructionsfor transmitting the first result. For example, the computer-readablestorage medium including executable instructions for monitoringmedication events 7800 can include instructions including: instructionsfor processing the determination if the accepted second data is withinthe provided set of medication intervention parameters into a secondresult; and instructions for transmitting the second result. Forexample, the computer-readable storage medium including executableinstructions for monitoring medication events 7800 can includeinstructions including: instructions for accepting third data from thecamera unit associated with the individual, the third data obtainedafter the activation of the at least one indicator in response to thesecond determination; instructions for analyzing the accepted third datafor the at least one attribute relating to the medication event;instructions for comparing the accepted third data with the provided setof medication intervention parameters for the individual; instructionsfor determining if the accepted third data is within the provided set ofmedication intervention parameters; and instructions for activating theat least one indicator in response to the third determination.

FIG. 79 illustrates a flowchart of a method 7900 for monitoringmedication events. These method steps can be carried out, for example,by a computer system (e.g. item 120 in FIG. 1). FIG. 79 shows that themethod includes a series of steps, 7910, 7920, 7930, 7940, 7950, 7960,7970, 7980, 7790, 7995. Method step 7910 includes accepting first datafrom a camera unit associated with an individual. Method step 7920includes providing a set of medication intervention parameters for theindividual. Method step 7930 includes comparing the accepted first datafrom the camera unit associated with the individual with the providedset of medication intervention parameters for the individual. Methodstep 7940 includes determining if the accepted first data is within theprovided set of medication intervention parameters. Method step 7950includes activating at least one indicator in response to the firstdetermination. Method step 7960 includes accepting second data from thecamera unit associated with the individual, the second data obtainedafter the activation of the at least one indicator. Method step 7970includes analyzing the accepted second data for at least one attributerelating to the medication event. Method step 7980 includes comparingthe accepted second data with the provided set of medicationintervention parameters for the individual. Method step 7990 includesdetermining if the accepted second data is within the provided set ofmedication intervention parameters. Method step 7995 includes activatingthe at least one indicator in response to the second determination.

In some embodiments, the flowchart of a method 7900 for monitoringmedication events illustrated in FIG. 79 includes additional aspects. Asillustrated in FIG. 79, method step 7910 includes accepting first datafrom a camera unit associated with an individual. Method step 7910 caninclude one or more additional steps. For example, method step 7910 caninclude accepting visual data and accepting non-visual data. Forexample, method step 7910 can include accepting data from a camera unitintegral to a mobile device. For example, method step 7910 can includeaccepting data from a camera unit integral to a fixed-location device.For example, method step 7910 can include accepting data including atleast two visual images. For example, method step 7910 can includeaccepting data including video data. For example, method step 7910 caninclude accepting data including near-infrared (IR) data. For example,method step 7910 can include accepting data including radio frequency(RF) data. For example, method step 7910 can include accepting dataincluding data from a micropower impulse radar (MIR) device. Forexample, method step 7910 can include accepting data including thermaldata. For example, method step 7910 can include accepting data includingaudio data.

As illustrated in FIG. 79, method step 7920 includes providing a set ofmedication intervention parameters for the individual. Method step 7920can include one or more additional steps. For example, method step 7920can include providing a set of medication intervention parameters forthe individual including time parameters. For example, method step 7920can include providing a set of medication intervention parameters forthe individual including visual parameters. For example, method step7920 can include providing a set of medication intervention parametersfor the individual including audio parameters. For example, method step7920 can include providing a set of medication intervention parametersfor the individual including near-infrared (IR) parameters. For example,method step 7920 can include providing a set of medication interventionparameters for the individual including thermal parameters. For example,method step 7920 can include providing a set of medication interventionparameters for the individual including micropower impulse radarparameters.

As shown in FIG. 79, method step 7930 includes comparing the acceptedfirst data from the camera unit associated with the individual with theprovided set of medication intervention parameters for the individual.Method step 7930 can include one or more additional steps. For example,method step 7930 can include comparing the accepted first data with atleast one minimum sufficiency parameter. For example, method step 7930can include comparing the accepted first data with a set of parametersassociated with the individual. For example, method step 7930 caninclude comparing the accepted first data with a range of sufficiencyparameters. For example, method step 7920 can include comparing theaccepted first data with a series of minimum medication interventionparameters.

As depicted in FIG. 79, method step 7940 includes determining if theaccepted first data is within the provided set of medicationintervention parameters. Method step 7940 can include one or moreadditional steps. For example, method step 7940 can include determiningthat the accepted first data either is within the provided set ofmedication intervention parameters or is not within the provided set ofmedication intervention parameters.

As shown in FIG. 79, method step 7950 includes activating at least oneindicator in response to the first determination. Method step 7950 caninclude one or more additional steps. For example, method step 7950 caninclude activating a visual indicator. For example, method step 7950 caninclude activating an audio indicator. For example, method step 7950 caninclude activating a vibratory indicator.

As depicted in FIG. 79, method step 7960 includes accepting second datafrom the camera unit associated with the individual, the second dataobtained after the activation of the at least one indicator. Method step7960 can include one or more additional steps. For example, method step7960 can include accepting second data from at least one camera unit,the second data including at least one time value. For example, methodstep 7960 can include accepting data including visual data, non-visualdata, and at least one time value.

As shown in FIG. 79, method step 7970 includes analyzing the acceptedsecond data for at least one attribute relating to the medication event.Method step 7970 can include one or more additional steps. For example,method step 7970 can include analyzing the accepted second data for theat least one attribute relating to a medication event. For example,method step 7970 can include analyzing the accepted second data for atleast one visual attribute. For example, method step 7970 can includeanalyzing the accepted second data for at least one non-visualattribute.

As illustrated in FIG. 79, method step 7980 includes comparing theaccepted second data with the provided set of medication interventionparameters for the individual. Method step 7980 can include one or moreadditional steps. For example, method step 7980 can include comparingboth visual data and non-visual data.

As depicted in FIG. 79, method step 7990 includes determining if theaccepted second data is within the provided set of medicationintervention parameters. Method step 7990 can include one or moreadditional steps. For example, method step 7990 can include determiningthat the accepted second data either is within the provided set ofmedication intervention parameters or is not within the provided set ofmedication intervention parameters.

As shown in FIG. 79, method step 7995 includes activating the at leastone indicator in response to the second determination. Method step 7995can include one or more additional steps. For example, method step 7995can include activating at least one visual indicator. For example,method step 7995 can include activating at least one audio indicator.For example, method step 7995 can include activating at least onevibratory indicator.

In some embodiments, the flowchart of a method 7900 for monitoringmedication events shown in FIG. 79 includes one or more additionalaspects. For example, the method can include: presenting at least oneattribute of the individual; and analyzing the accepted first data forthe at least one attribute of the individual. For example, the methodcan include: presenting at least one attribute of the individual; andanalyzing the accepted second data for the at least one attribute of theindividual. For example, the method can include: saving the acceptedfirst data in a memory. For example, the method can include: saving theaccepted second data in a memory. For example, the method can include:processing the at least one accepted first data; processing the at leastone accepted second data; integrating the processed at least oneaccepted first data and the processed at least one accepted second datainto a medication record; and saving the medication record in a memory.For example, the method can include: processing the determination if theaccepted first data is within the provided set of medicationintervention parameters into a first result; and transmitting the firstresult. For example, the method can include: processing thedetermination if the accepted second data is within the provided set ofmedication intervention parameters into a second result; andtransmitting the second result. For example, the method can include:accepting third data from the camera unit associated with theindividual, the third data obtained after the activation of the at leastone indicator in response to the second determination; analyzing theaccepted third data for the at least one attribute relating to themedication event; comparing the accepted third data with the providedset of medication intervention parameters for the individual;determining if the accepted third data is within the provided set ofmedication intervention parameters; and activating the at least oneindicator in response to the third determination.

FIG. 80 illustrates diagram of aspects of a system for monitoringmedication events relating to an individual. The system can be acomputer system such as depicted in FIG. 1 and described herein. Thesystem 8000 depicted in FIG. 80 includes electrical circuitry. Thecircuitry of the system 8000 is configured to carry out a series oflogical processes. As illustrated in FIG. 80, a system 8000 formonitoring medication events relating to an individual includes one ormore circuitry components 8010, 8020, 8030, 8040, 8050, 8060, 8070,8080, 8090, 8095. The circuitry is configured to carry out specificprocesses.

The system 8000 includes circuitry 8010 for providing a set ofattributes for an individual, the set of attributes identifiable incamera unit data. The system 8000 includes circuitry 8020 for providinga set of medication condition parameters for the individual, the set ofmedication condition parameters identifiable in the camera unit data.The system 8000 includes circuitry 8030 for accepting first data from atleast one camera unit. The system 8000 includes circuitry 8040 forcomparing the accepted first data with the provided set of attributesfor the individual and with the provided set of medication conditionparameters for the individual. The system 8000 includes circuitry 8050for determining, from the comparison, if the accepted first dataincludes attributes of the individual and meets the medication conditionparameters. The system 8000 includes circuitry 8060 for initiating afirst medication intervention event, dependent on the determination fromthe comparison. The system 8000 includes circuitry 8070 for acceptingsecond data from the at least one camera unit. The system 8000 includescircuitry 8080 for providing a set of parameters for the firstmedication intervention event, the set of first medication interventionparameters identifiable in the camera unit data. The system 8000includes circuitry 8085 for comparing the accepted second data with theprovided set of attributes for the individual and with the provided setof parameters for the first medication intervention event. The system8000 includes circuitry 8090 for determining, from the comparison, ifthe accepted second data includes attributes of the individual and meetsthe parameters for the first medication intervention event. The system8000 includes circuitry 8095 for activating at least one indicator inresponse to the second determination.

FIG. 81 illustrates that, in some embodiments, the system 8000 includingcircuitry 8010 can include one or more of circuitry 8100, 8110, 8120,8130, 8140. The system 8000 includes circuitry 8010 for providing a setof attributes for an individual, the set of attributes identifiable incamera unit data. In some embodiments, circuitry 8010 includes circuitry8100 for: providing visual attributes; and circuitry for providingnon-visual attributes. For example, the circuitry can provide attributesfrom camera data as well as provide attributes from an attachedmicrophone. In some embodiments, circuitry 8010 includes circuitry 8110for providing a set of attributes identifiable in the camera unit dataoriginating with a mobile device. For example, the circuitry can providea set of attributes identifiable in the camera unit data originatingfrom at least one smartphone, PDA, tablet computer, or laptop. In someembodiments, circuitry 8010 includes circuitry 8120 for providing a setof attributes identifiable in the camera unit data originating with afixed position camera unit. For example, the circuitry can provide a setof attributes identifiable in the camera unit data originating with afixed position camera unit configured to be attached to a wall. In someembodiments, circuitry 8010 includes circuitry 8130 for providing a setof attributes identifiable in the camera unit data including at leasttwo visual images. For example, the circuitry can provide a set ofattributes identifiable in the camera unit data including at least twovisual images taken from the same camera unit at different times. Forexample, the circuitry can provide a set of attributes identifiable inthe camera unit data including at least two visual images taken from twodifferent camera units. In some embodiments, circuitry 8010 includescircuitry 8140 for providing a set of attributes identifiable in thecamera unit data including video data. For example, the circuitry canprovide a set of attributes identifiable in the camera unit dataincluding video data taken with the camera unit during the duration ofan expected medication event.

FIG. 82 shows that, in some embodiments, the system 8000 includingcircuitry 8010 can include one or more of circuitry 8200, 8210, 8220,8230, 8240. The system 8000 includes circuitry 8010 for providing a setof attributes for an individual, the set of attributes identifiable incamera unit data. In some embodiments, circuitry 8010 includes circuitry8200 for providing a set of attributes identifiable in the camera unitdata including near-infrared (IR) data. For example, the circuitry canprovide attributes from camera data taken in the near-IR spectrum. Insome embodiments, circuitry 8010 includes circuitry 8210 for providing aset of attributes identifiable in the camera unit data including thermaldata. For example, the circuitry can provide a set of attributesidentifiable in the camera unit data originating from a camera unit thatincludes a temperature monitor device. In some embodiments, circuitry8010 includes circuitry 8220 for providing a set of attributesidentifiable in the camera unit data including audio data. For example,the circuitry can provide a set of attributes identifiable in the cameraunit data originating with a microphone attached to the camera unit. Insome embodiments, circuitry 8010 includes circuitry 8230 for providing aset of attributes identifiable in the camera unit data includingmicropower impulse radar (MIR) data. For example, the camera unit caninclude a MIR device. In some embodiments, circuitry 8010 includescircuitry 8240 for providing a set of attributes specific to theindividual. For example, the circuitry can provide a set of attributesidentifiable in the camera unit data including aspects of the facialfeatures of the individual.

FIG. 83 shows that, in some embodiments, the system 8000 can includeadditional features. The system 8000 includes circuitry 8020 forproviding a set of medication condition parameters for the individual,the set of medication condition parameters identifiable in the cameraunit data. FIG. 83 shows that in some embodiments, circuitry 8020 caninclude one or more of circuitry 8300, 8310, 8320, 8330, 8340. Circuitry8300 includes circuitry for providing visual parameters and providingnon-visual parameters. For example, the circuitry can provide parameterfor data originating from the optic features of a camera unit, as wellas parameters for data originating from a microphone attached to thecamera unit. Circuitry 8310 includes circuitry for providing a set ofparameters identifiable in the camera unit data originating with amobile device. For example, the data can originate with a camera unitintegral to a PDA, laptop, or tablet computing device. Circuitry 8320includes circuitry for providing a set of parameters identifiable in thecamera unit data originating with a fixed position camera unit. Forexample, the data can originate with a camera unit integral to a cameraunit affixed to a post or beam of a building. Circuitry 8330 includescircuitry for providing a set of parameters including at least twovisual parameters. For example, the visual parameters can includebrightness parameters as well as pixel size parameters. Circuitry 8340includes circuitry for providing a set of parameters identifiable invideo data. For example, the data can originate with a camera unitincluding video capabilities.

FIG. 84 depicts that, in some embodiments, the system 8000 can includeadditional features. The system 8000 includes circuitry 8020 forproviding a set of medication condition parameters for the individual,the set of medication condition parameters identifiable in the cameraunit data. FIG. 84 shows that in some embodiments, circuitry 8020 caninclude one or more of circuitry 8400, 8410, 8420, 8430, 8440. Circuitry8400 includes circuitry for a set of parameters including audioparameters. For example, the circuitry can provide parameters for dataoriginating from a microphone attached to the camera unit, such aspitch, decibel level, or tone. Circuitry 8410 includes circuitry forproviding a set of parameters including thermal parameters. For example,the data can originate with a camera unit including a thermal reader,and the parameters can include high and low temperature readings.Circuitry 8420 includes circuitry for providing a set of parametersincluding near-infrared (IR) parameters. For example, the data canoriginate with a camera unit including near-IR detection capabilities.Circuitry 8430 includes circuitry for providing a set of parametersincluding radio frequency (RF) parameters. For example, the visualparameters can include RFID code parameters. Circuitry 8440 includescircuitry for providing a set of parameters including micropower impulseradar (MIR) parameters. For example, the data can originate with acamera unit integrated with a MIR device.

FIG. 85 shows that, in some embodiments, the system 8000 can includeadditional features. The system 8000 includes circuitry 8020 forproviding a set of medication condition parameters for the individual,the set of medication condition parameters identifiable in the cameraunit data. FIG. 85 illustrates that in some embodiments, circuitry 8020can include circuitry 8500. Circuitry 8500 includes circuitry forproviding a set of parameters specific to the individual. For example,the circuitry 8500 can include providing a set of parameters such as eyecolor, height, facial shape, and similar parameters specific to theindividual.

FIG. 85 also illustrates that, in some embodiments, circuitry 8030 caninclude one or more of circuitry 8510, 8520, 8530, 8540, 8550, 8560.Circuitry 8030 includes circuitry for accepting first data from at leastone camera unit. Circuitry 8510 includes circuitry for accepting bothvisual and non-visual data. For example, the circuitry can be configuredto accept visual data obtained by a camera unit and audio data from anattached microphone. Circuitry 8520 includes circuitry for acceptingvideo data. Circuitry 8530 includes circuitry for accepting audio data.Circuitry 8540 includes circuitry for accepting thermal data. Circuitry8550 includes circuitry for accepting near-infrared (IR) data. Circuitry8550 includes circuitry for accepting radio frequency (RF) data.

FIG. 86 depicts that, in some embodiments, the system 8000 can includeadditional features. The system 8000 includes circuitry 8030 foraccepting first data from at least one camera unit. FIG. 86 illustratesthat in some embodiments, circuitry 8030 can include one or more ofcircuitry 8600, 8610, 8620, 8630. Circuitry 8600 includes circuitry foraccepting micropower impulse radar (MIR) data. Circuitry 8610 includescircuitry for accepting data from a camera unit integral to a mobiledevice. Circuitry 8620 includes circuitry for accepting data from thecamera unit integral to a fixed-position device. Circuitry 8630 includescircuitry for accepting data from a plurality of camera units. Forexample, the circuitry can accept data from a plurality of camera unitsintegrated into one or more mobile devices, or a plurality offixed-position camera units, or a combination thereof.

FIG. 86 also shows that, in some embodiments, circuitry 8040 can includecircuitry 8640. Circuitry 8040 includes circuitry for comparing theaccepted first data with the provided set of attributes for theindividual and with the provided set of medication condition parametersfor the individual. Circuitry 8640 includes circuitry for comparing asubset of the accepted first data with the provided set of medicationcondition parameters for the individual and with the provided set ofmedication condition parameters for the individual.

FIG. 87 shows additional features of the system 8000 for monitoringmedication events. FIG. 87 illustrates that circuitry 8040 can includecircuitry 8700. Circuitry 8700 includes circuitry for comparing visualand non-visual components of the accepted first data with the providedset of medication condition parameters for the individual and with theprovided set of medication condition parameters for the individual. FIG.87 also illustrates that, in some embodiments, circuitry 8050 caninclude circuitry 8710. Circuitry 8050 includes circuitry fordetermining, from the comparison, if the accepted first data includesattributes of the individual and meets the medication conditionparameters. Circuitry 8710 includes circuitry for determining, from thecomparison, if the accepted first data meets both visual and non-visualaspects of the medication condition parameters.

FIG. 88 depicts additional features of the system 8000 for monitoringmedication events. FIG. 88 shows that circuitry 8060 can, in someembodiments, include one or more of circuitry 8800, 8810. Circuitry 8060includes circuitry for initiating the first medication interventionevent, dependent on the determination from the comparison. Circuitry8800 includes circuitry for activating at least one indicator. Forexample, the circuitry can function to activate at least one indicatorattached to the computer system (i.e. item 120 in FIG. 1). Circuitry8810 includes circuitry for activating at least one alarm. For example,the circuitry can function to activate at least one alarm attached tothe computer system (i.e. item 120 in FIG. 1).

FIG. 88 also illustrates that, in some embodiments, circuitry 8070 caninclude on or more of circuitry 8820, 8830, 8840. Circuitry 8070includes the circuitry for accepting the second data from the at leastone camera unit. Circuitry 8820 includes circuitry for accepting seconddata including both visual and non-visual aspects. Circuitry 8830includes circuitry for accepting second data including at least one timevalue. Circuitry 8840 includes circuitry for accepting data including apersonal identifier of the individual. For example, the circuitry can beconfigured to accept data including an RFID code identifying theindividual, such as from an RF signal reflected from an ID band. Forexample, the circuitry can be configured to accept data including apersonal identifier such as a name or ID number input into the system,such as from a keyboard integrated into a monitoring device (e.g. item160 in FIG. 1).

FIG. 89 shows that, in some embodiments, circuitry 8070 includescircuitry 8900. Circuitry 8070 includes the circuitry for accepting thesecond data from the at least one camera unit. Circuitry 8900 includesaccepting data from a plurality of camera units. FIG. 89 also showsthat, in some embodiments, circuitry 8080 includes one or more ofcircuitry 8910, 8920, 8930. Circuitry 8080 includes providing the set ofparameters for the first medication intervention event, the set ofmedication intervention parameters identifiable in the camera unit data.Circuitry 8910 includes circuitry for providing a set of parametersincluding minimum values. For example, the minimum values can includeminimum brightness values or numbers of pixels. Circuitry 8920 includescircuitry for providing a set of both visual and non-visual parameters.Circuitry 8930 includes circuitry for providing a set of parametersincluding a range of values. For example, the circuitry can include arange of acceptable brightness values or a range of pixel levels in thedata.

FIG. 90 shows that, in some embodiments, circuitry 8090 includes one ormore of circuitry 9000, 9010. Circuitry 8090 includes circuitry fordetermining, from the comparison, if the accepted second data includesattributes of the individual and meets the parameters for the firstmedication intervention event. Circuitry 9000 includes circuitry forcomparing the accepted data including both visual and non-visual datawith the provided set of attributes for the individual and with theprovided set of medication intervention parameters for the individual.Circuitry 9010 includes circuitry for determining, from the comparison,if the accepted second data meets both visual and non-visual aspects ofthe medication condition parameters. FIG. 90 also shows that, in someembodiments, circuitry 9095 includes circuitry 9020. Circuitry 9095includes circuitry for activating the at least one indicator in responseto the second determination. Circuitry 9020 includes circuitry foractivating at least one visual indicator. For example, circuitry can beconfigured to activate at least one visual indicator on a display unitattached to a main computing unit within the computer system (e.g. item125 in FIG. 1).

FIG. 91 shows that, in some embodiments, the system 8000 for monitoringmedication events includes additional components in addition tocircuitry 8010, 8020, 8030, 8040, 8050, 8060, 8070, 8080, 8090, 8095.FIG. 91 illustrates that the system can include one or more of circuitry9100, 9110, 9120, 9230. Circuitry 9100 includes circuitry for saving thefirst determination in a memory. Circuitry 9110 includes circuitry forsaving the second determination in a memory. For example, the system cansave the first or second determination in a memory within the hard driveof a main computing unit (e.g. item 125 in FIG. 1). Circuitry 9120includes circuitry for saving the accepted first data in a memory.Circuitry 9130 includes circuitry for saving the accepted second data ina memory. For example, the system can save the accepted first or seconddata in a memory within the hard drive of a main computing unit (e.g.item 125 in FIG. 1).

FIG. 92 depicts that, in some embodiments, the system 8000 formonitoring medication events includes additional components in additionto circuitry 8010, 8020, 8030, 8040, 8050, 8060, 8070, 8080, 8090, 8095.FIG. 92 shows that the system can include one or more of circuitry 9200,9210. Circuitry 9200 includes: circuitry for processing the at least oneaccepted first data; circuitry for processing the at least one acceptedsecond data; circuitry for integrating the processed at least oneaccepted first data and the processed at least one accepted second datainto a medication record; and circuitry for saving the medication recordin a memory. Circuitry 9210 includes: circuitry for processing the ifthe accepted first data includes attributes of the individual and meetsthe medication condition parameters into a first result; and circuitryfor transmitting the first result. For example, the first result can betransmitted to a secondary computing unit (e.g. items 130, 135 in FIG.1).

FIG. 93 illustrates that, in some embodiments, the system 8000 formonitoring medication events includes additional components in additionto circuitry 8010, 8020, 8030, 8040, 8050, 8060, 8070, 8080, 8090, 8095.FIG. 93 depicts that the system can include one or more of circuitry9300, 9310. Circuitry 9300 includes circuitry for indicating, to atleast one system user, the initiating a first medication interventionevent. Circuitry 9310 includes: circuitry for indicating, to at leastone system user, the determining, from the comparison, if the acceptedsecond data includes attributes of the individual and meets theparameters for the first medication intervention event.

FIG. 94 depicts that, in some embodiments, the system 8000 formonitoring medication events includes additional components in additionto circuitry 8010, 8020, 8030, 8040, 8050, 8060, 8070, 8080, 8090, 8095.FIG. 94 depicts that the system can include circuitry 9400. Circuitry9400 includes: circuitry for accepting third data from the at least onecamera unit; circuitry for providing a set of parameters for a secondmedication intervention event, the set of second medication interventionparameters identifiable in camera unit data; circuitry for comparing theaccepted third data with the provided set of attributes for theindividual and with the provided set of parameters for the secondmedication intervention event; circuitry for determining, from thecomparison, if the accepted third data includes attributes of theindividual and meets the parameters for the second medicationintervention event; and circuitry for activating at least one indicatorin response to the third determination.

FIG. 95 illustrates aspects of a computer system 120 including at leastone main computing unit 125. Although a single main computing unit 125is illustrated in FIG. 95, in some embodiments there may be a pluralityof main computing units 125. A main computing unit 125 includescomputer-readable storage medium including executable instructions formonitoring medication events 9500. The computer-readable storage mediumincluding executable instructions for monitoring medication eventsrelating to an individual 9500 includes instructions 9510, 9520, 9530,9540, 9550, 9560, 9570, 9580, 9585, 9590, 9595. Instructions 9510include instructions for providing a set of attributes for anindividual, the set of attributes identifiable in camera unit data.Instructions 9520 include instructions for providing a set of medicationcondition parameters for the individual, the set of medication conditionparameters identifiable in camera unit data. Instructions 9530 includeinstructions for accepting first data from at least one camera unit.Instructions 9540 include instructions for comparing the accepted firstdata with the provided set of attributes for the individual and with theprovided set of medication condition parameters for the individual.Instructions 9550 include instructions for determining, from thecomparison, if the accepted first data includes attributes of theindividual and meets the medication condition parameters. Instructions9560 include instructions for initiating a first medication interventionevent, dependent on the determination from the comparison. Instructions9570 include instructions for accepting second data from the at leastone camera unit. Instructions 9580 include instructions for providing aset of parameters for the first medication intervention event, the setof first medication intervention parameters identifiable in camera unitdata. Instructions 9585 include instructions for comparing the acceptedsecond data with the provided set of attributes for the individual andwith the provided set of parameters for the first medicationintervention event. Instructions 9590 include instructions fordetermining, from the comparison, if the accepted second data includesattributes of the individual and meets the parameters for the firstmedication intervention event. Instructions 9595 include instructionsfor activating at least one indicator in response to the seconddetermination.

As shown in FIG. 95, instructions 9510 include instructions forproviding a set of attributes for an individual, the set of attributesidentifiable in camera unit data. In some embodiments, instructions 9510can include one or more additional instructions. In some embodiments,instructions 9510 include: instructions for providing visual attributes;and instructions for providing non-visual attributes. In someembodiments, instructions 9510 include instructions for providing a setof attributes identifiable in camera unit data originating with a mobiledevice. In some embodiments, instructions 9510 include instructions forproviding a set of attributes identifiable in camera unit dataoriginating with a fixed position camera unit. In some embodiments,instructions 9510 include instructions for providing a set of attributesidentifiable in camera unit data including at least two visual images.In some embodiments, instructions 9510 include instructions forproviding a set of attributes identifiable in camera unit data includingvideo data. In some embodiments, instructions 9510 include instructionsfor providing a set of attributes identifiable in camera unit dataincluding near-infrared (IR) data. In some embodiments, instructions9510 include instructions for providing a set of attributes identifiablein camera unit data including thermal data. In some embodiments,instructions 9510 include instructions for providing a set of attributesidentifiable in camera unit data including audio data. In someembodiments, instructions 9510 include instructions for providing a setof attributes identifiable in camera unit data including micropowerimpulse radar (MIR) data. In some embodiments, instructions 9510 includeinstructions for providing a set of attributes specific to theindividual.

As depicted in FIG. 95, instructions 9520 include instructions forproviding the set of medication condition parameters for the individual,the set of medication condition parameters identifiable in the cameraunit data. In some embodiments, instructions 9520 can include one ormore additional instructions. In some embodiments, instructions 9520include instructions for providing visual parameters and providingnon-visual parameters. In some embodiments, instructions 9520 includeinstructions for providing a set of parameters identifiable in cameraunit data originating with a mobile device. In some embodiments,instructions 9520 include instructions for providing a set of parametersidentifiable in camera unit data originating with a fixed positioncamera unit. In some embodiments, instructions 9520 include instructionsfor providing a set of parameters including at least two visualparameters. In some embodiments, instructions 9520 include instructionsfor providing a set of parameters identifiable in video data. In someembodiments, instructions 9520 include instructions for providing a setof parameters including audio parameters. In some embodiments,instructions 9520 include instructions for providing a set of parametersincluding thermal parameters. In some embodiments, instructions 9520include instructions for providing a set of parameters includingnear-infrared (IR) parameters. In some embodiments, instructions 9520include instructions for providing a set of parameters including radiofrequency (RF) parameters. In some embodiments, instructions 9520include instructions for providing a set of parameters includingmicropower impulse radar (MIR) parameters. In some embodiments,instructions 9520 include instructions for providing a set of parametersspecific to the individual.

As shown in FIG. 95, instructions 9530 include instructions foraccepting the first data from the at least one camera unit. In someembodiments, instructions 9530 can include one or more additionalinstructions. In some embodiments, instructions 9530 includeinstructions for accepting both visual and non-visual data. In someembodiments, instructions 9530 include instructions for accepting videodata. In some embodiments, instructions 9530 include instructions foraccepting audio data. In some embodiments, instructions 9530 includeinstructions for accepting thermal data. In some embodiments,instructions 9530 include instructions for accepting near-infrared (IR)data. In some embodiments, instructions 9530 include instructions foraccepting radio frequency (RF) data. In some embodiments, instructions9530 include instructions for accepting micropower impulse radar (MIR)data. In some embodiments, instructions 9530 include instructions foraccepting data from a camera unit integral to a mobile device. In someembodiments, instructions 9530 include instructions for accepting datafrom a camera unit integral to a fixed-position device. In someembodiments, instructions 9530 include instructions for accepting datafrom a plurality of camera units.

As shown in FIG. 95, instructions 9540 include instructions forcomparing the accepted first data with the provided set of attributesfor the individual and with the provided set of medication conditionparameters for the individual. In some embodiments, instructions 9540can include one or more additional instructions. In some embodiments,instructions 9540 include instructions for comparing a subset of theaccepted first data with the provided set of medication conditionparameters for the individual and with the provided set of medicationcondition parameters for the individual. In some embodiments,instructions 9540 include instructions for comparing visual andnon-visual components of the accepted first data with the provided setof medication condition parameters for the individual and with theprovided set of medication condition parameters for the individual.

As depicted in FIG. 95, instructions 9550 include instructions fordetermining, from the comparison, if the accepted first data includesattributes of the individual and meets the medication conditionparameters. In some embodiments, instructions 9550 can include one ormore additional instructions. In some embodiments, instructions 9550include instructions for determining, from the comparison, if theaccepted first data meets both visual and non-visual aspects of themedication condition parameters.

As shown in FIG. 95, instructions 9560 include instructions forinitiating the first medication intervention event, dependent on thedetermination from the comparison. In some embodiments, instructions9560 can include one or more additional instructions. In someembodiments, instructions 9560 include instructions for activating atleast one indicator. In some embodiments, instructions 9560 includeinstructions for activating at least one alarm. For example, theinstructions can cause the system to activate at least one indicatorand/or at least one alarm attached to a main computing unit (e.g. item120 in FIG. 95).

As illustrated in FIG. 95, instructions 9570 include instructions foraccepting the second data from the at least one camera unit. In someembodiments, instructions 9570 can include one or more additionalinstructions. In some embodiments, instructions 9570 includeinstructions for accepting second data including both visual andnon-visual aspects. In some embodiments, instructions 9570 includeinstructions for accepting second data including at least one timevalue. In some embodiments, instructions 9570 include instructions foraccepting data including a personal identifier of the individual. Insome embodiments, instructions 9570 include instructions for acceptingdata from a plurality of camera units. For example, the system caninclude instructions for accepting data from a plurality of monitoringdevices (e.g. item 110 in FIG. 1) that are fixed camera units affixed tothe walls of a room for the medication event (e.g. a therapy room).

As shown in FIG. 95, instructions 9580 include instructions providingthe set of parameters for the first medication intervention event, theset of medication intervention parameters identifiable in the cameraunit data. In some embodiments, instructions 9580 can include one ormore additional instructions. In some embodiments, instructions 9580include instructions for providing a set of parameters including minimumvalues. In some embodiments, instructions 9580 include instructions forproviding a set of both visual and non-visual parameters. In someembodiments, instructions 9580 include instructions for providing a setof parameters including a range of values.

As depicted in FIG. 95, instructions 9590 include instructions fordetermining, from the comparison, if the accepted second data includesattributes of the individual and meets the parameters for the firstmedication intervention event. In some embodiments, instructions 9590can include one or more additional instructions. In some embodiments,instructions 9590 include instructions for comparing accepted dataincluding both visual and non-visual data with the provided set ofattributes for the individual and with the provided set of medicationintervention parameters for the individual. In some embodiments,instructions 9590 include instructions for determining, from thecomparison, if the accepted second data meets both visual and non-visualaspects of the medication condition parameters.

As illustrated in FIG. 95, instructions 9595 include instructions foractivating the at least one indicator in response to the seconddetermination. In some embodiments, instructions 9595 can include one ormore additional instructions. In some embodiments, instructions 9595include instructions for activating at least one visual indicator.

In some embodiments, the computer-readable storage medium includingexecutable instructions for monitoring medication events 9500 includesone or more sets of additional instructions. For example, thecomputer-readable storage medium including executable instructions formonitoring medication events 9500 can include instructions for savingthe first determination in a memory. For example, the computer-readablestorage medium including executable instructions for monitoringmedication events 9500 can include instructions for saving the seconddetermination in a memory. For example, the computer-readable storagemedium including executable instructions for monitoring medicationevents 9500 can include instructions for saving the accepted first datain a memory. For example, the computer-readable storage medium includingexecutable instructions for monitoring medication events 9500 caninclude instructions for saving the accepted second data in a memory.For example, the computer-readable storage medium including executableinstructions for monitoring medication events 9500 can include:instructions for processing the at least one accepted first data;instructions for processing the at least one accepted second data;instructions for integrating the processed at least one accepted firstdata and the processed at least one accepted second data into amedication record; and instructions for saving the medication record ina memory. For example, the computer system (e.g. item 120 in FIG. 95)can include memory units, such as memory within a main computing unit(e.g. item 125 in FIG. 95) or additional computer memory storage deviceswithin the computer system.

In some embodiments, the computer-readable storage medium includingexecutable instructions for monitoring medication events 9500 includesone or more sets of additional instructions. For example, thecomputer-readable storage medium including executable instructions formonitoring medication events 9500 can include: instructions forprocessing the if the accepted first data includes attributes of theindividual and meets the medication condition parameters into a firstresult; and instructions for transmitting the first result. For example,the first result can be transmitted within the computer system (e.g.item 120 in FIG. 95) from a transmitter attached to a main computingunit (e.g. item 125 in FIG. 95) to a secondary computing unit (e.g.items 140, 145 in FIG. 1).

In some embodiments, the computer-readable storage medium includingexecutable instructions for monitoring medication events 9500 includesone or more sets of additional instructions. For example, thecomputer-readable storage medium including executable instructions formonitoring medication events 9500 can include instructions forindicating, to at least one system user, the initiating a firstmedication intervention event. For example, the computer-readablestorage medium including executable instructions for monitoringmedication events 9500 can include instructions for indicating, to atleast one system user, the determining, from the comparison, if theaccepted second data includes attributes of the individual and meets theparameters for the first medication intervention event. In someembodiments, the computer-readable storage medium including executableinstructions for monitoring medication events 9500 includes one or moresets of additional instructions. For example, the computer-readablestorage medium including executable instructions for monitoringmedication events 9500 can include: instructions for accepting thirddata from the at least one camera unit; instructions for providing a setof parameters for a second medication intervention event, the set ofsecond medication intervention parameters identifiable in camera unitdata; instructions for comparing the accepted third data with theprovided set of attributes for the individual and with the provided setof parameters for the second medication intervention event; instructionsfor determining, from the comparison, if the accepted third dataincludes attributes of the individual and meets the parameters for thesecond medication intervention event; and instructions for activating atleast one indicator in response to the third determination. For example,a main computing unit (e.g. item 125 in FIG. 95) can include a monitordevice, which can be configured to respond to instructions of the systemfor making an indication.

FIG. 96 illustrates a flowchart of a method 9600 for monitoringmedication events. These method steps can be carried out, for example,by a computer system (e.g. item 120 in FIG. 1). FIG. 96 shows that themethod includes a series of steps, 9610, 9620, 9630, 9640, 9650, 9660,9670, 9680, 9685, 9690, 9695. Method step 9610 includes providing a setof attributes for an individual, the set of attributes identifiable incamera unit data. Method step 9620 includes providing a set ofmedication condition parameters for the individual, the set ofmedication condition parameters identifiable in camera unit data. Methodstep 9630 includes accepting first data from at least one camera unit.Method step 9640 includes comparing the accepted first data with theprovided set of attributes for the individual and with the provided setof medication condition parameters for the individual. Method step 9650includes determining, from the comparison, if the accepted first dataincludes attributes of the individual and meets the medication conditionparameters. Method step 9660 includes initiating a first medicationintervention event, dependent on the determination from the comparison.Method step 9670 includes accepting second data from the at least onecamera unit. Method step 9680 includes providing a set of parameters forthe first medication intervention event, the set of first medicationintervention parameters identifiable in camera unit data. Method step9685 includes comparing the accepted second data with the provided setof attributes for the individual and with the provided set of parametersfor the first medication intervention event. Method step 9690 includesdetermining, from the comparison, if the accepted second data includesattributes of the individual and meets the parameters for the firstmedication intervention event. Method step 9695 includes activating atleast one indicator in response to the second determination.

In some embodiments, the flowchart of a method 9600 for monitoringmedication events illustrated in FIG. 96 includes additional aspects. Asillustrated in FIG. 96, method step 9610 includes providing a set ofattributes for an individual, the set of attributes identifiable incamera unit data. Method step 9610 can include one or more additionalsteps. For example, method step 9610 can include: providing visualattributes; and providing non-visual attributes. For example, methodstep 9610 can include providing a set of attributes identifiable incamera unit data originating with a mobile device. For example, methodstep 9610 can include providing at set of attributes identifiable incamera unit data originating with a fixed position camera unit. Forexample, method step 9610 can include providing a set of attributesidentifiable in camera unit data including at least two visual images.For example, method step 9610 can include providing a set of attributesidentifiable in camera unit data including video data. For example,method step 9610 can include providing a set of attributes identifiablein camera unit data including near-infrared (IR) data. For example,method step 9610 can include providing a set of attributes identifiablein camera unit data including thermal data. For example, method step9610 can include providing a set of attributes identifiable in cameraunit data including audio data. For example, method step 9610 caninclude providing a set of attributes identifiable in camera unit dataincluding micropower impulse radar (MIR) data. For example, method step9610 can include providing a set of attributes specific to theindividual.

As shown in FIG. 96, method step 9620 includes providing a set ofmedication condition parameters for the individual, the set ofmedication condition parameters identifiable in camera unit data. Methodstep 9620 can include one or more additional steps. For example, methodstep 9620 can include providing visual parameters and providingnon-visual parameters. For example, method step 9620 can includeproviding a set of parameters identifiable in camera unit dataoriginating with a mobile device. For example, method step 9620 caninclude providing a set of parameters identifiable in camera unit dataoriginating with a fixed position camera unit. For example, method step9620 can include providing a set of parameters including at least twovisual parameters. For example, method step 9620 can include providing aset of parameters identifiable in video data. For example, method step9620 can include providing a set of parameters including audioparameters. For example, method step 9620 can include providing a set ofparameters including thermal parameters. For example, method step 9620can include providing a set of parameters including near-infrared (IR)parameters. For example, method step 9620 can include providing a set ofparameters including radio frequency (RF) parameters. For example,method step 9620 can include providing a set of parameters includingmicropower impulse radar (MIR) parameters. For example, method step 9620can include providing a set of parameters specific to the individual.

As illustrated in FIG. 96, method step 9630 includes accepting firstdata from at least one camera unit. Method step 9630 can include one ormore additional steps. For example, method step 9630 can includeaccepting both visual and non-visual data. For example, method step 9630can include accepting video data. For example, method step 9630 caninclude accepting audio data. For example, method step 9630 can includeaccepting thermal data. For example, method step 9630 can includeaccepting near-infrared (IR) data. For example, method step 9630 caninclude accepting radio frequency (RF) data. For example, method step9630 can include accepting micropower impulse radar (MIR) data. Forexample, method step 9630 can include accepting data from a camera unitintegral to a mobile device. For example, method step 9630 can includeaccepting data from a camera unit integral to a fixed-position device.For example, method step 9630 can include accepting data from aplurality of camera units.

As depicted in FIG. 96, method step 9640 includes comparing the acceptedfirst data with the provided set of attributes for the individual andwith the provided set of medication condition parameters for theindividual. Method step 9640 can include one or more additional steps.For example, method step 9640 can include comparing a subset of theaccepted first data with the provided set of medication conditionparameters for the individual and with the provided set of medicationcondition parameters for the individual. Method step 9640 can includecomparing visual and non-visual components of the accepted first datawith the provided set of medication condition parameters for theindividual and with the provided set of medication condition parametersfor the individual.

As depicted in FIG. 96, method step 9650 includes determining, from thecomparison, if the accepted first data includes attributes of theindividual and meets the medication condition parameters. Method step9650 can include one or more additional steps. For example, method step9650 can include determining, from the comparison, if the accepted firstdata meets both visual and non-visual aspects of the medicationcondition parameters.

As shown in FIG. 96, method step 9660 includes initiating a firstmedication intervention event, dependent on the determination from thecomparison. Method step 9660 can include one or more additional steps.For example, method step 9660 can include activating at least oneindicator. For example, method step 9660 can include activating at leastone alarm.

As depicted in FIG. 96, method step 9670 includes accepting second datafrom the at least one camera unit. Method step 9670 can include one ormore additional steps. For example, method step 9670 can includeaccepting second data including both visual and non-visual aspects. Forexample, method step 9670 can include accepting second data including atleast one time value. For example, method step 9670 can includeaccepting data including a personal identifier of the individual. Forexample, method step 9670 can include accepting data from a plurality ofcamera units.

As shown in FIG. 96, method step 9680 includes providing a set ofparameters for the first medication intervention event, the set of firstmedication intervention parameters identifiable in camera unit data.Method step 9680 can include one or more additional steps. For example,method step 9680 can include providing a set of parameters includingminimum values. For example, method step 9680 can include providing aset of both visual and non-visual parameters. For example, method step9680 can include providing a set of parameters including a range ofvalues.

As illustrated in FIG. 96, method step 9690 includes determining, fromthe comparison, if the accepted second data includes attributes of theindividual and meets the parameters for the first medicationintervention event. Method step 9690 can include one or more additionalsteps. For example, method step 9690 can include comparing accepted dataincluding both visual and non-visual data with the provided set ofattributes for the individual and with the provided set of medicationintervention parameters for the individual. For example, method step9690 can include determining, from the comparison, if the acceptedsecond data meets both visual and non-visual aspects of the medicationcondition parameters.

As shown in FIG. 96, method step 9695 includes activating at least oneindicator in response to the second determination. Method step 9695 caninclude one or more additional steps. For example, method step 9695 caninclude activating at least one visual indicator.

The method flowchart illustrated in FIG. 96 can also include additionalsteps. For example, the method 9600 can include saving the firstdetermination in a memory. For example, the method 9600 can includesaving the second determination in a memory. For example, the method9600 can include saving the accepted first data in a memory. Forexample, the method 9600 can include saving the accepted second data ina memory. For example, the method 9600 can include: processing the atleast one accepted first data; processing the at least one acceptedsecond data; integrating the processed at least one accepted first dataand the processed at least one accepted second data into a medicationrecord; and saving the medication record in a memory. A memory can, forexample, be a computer memory integrated with the computer system (e.g.item 120 in FIG. 1).

The method flowchart depicted in FIG. 96 can also include additionalsteps. For example, the method 9600 can include: processing the if theaccepted first data includes attributes of the individual and meets themedication condition parameters into a first result; and transmittingthe first result. A transmitter can, for example, be integrated into thecomputer system (e.g. item 120 in FIG. 1) and transmit a result from themain computing unit (e.g. item 125 in FIG. 1) to one or more secondarycomputing units (e.g. items 130, 135 in FIG. 1).

The method flowchart shown in FIG. 96 can also include additional steps.For example, the method 9600 can include indicating, to at least onesystem user, the initiating a first medication intervention event. Forexample, the method 9600 can include indicating, to at least one systemuser, the determining, from the comparison, if the accepted second dataincludes attributes of the individual and meets the parameters for thefirst medication intervention event. For example, the method 9600 caninclude accepting third data from the at least one camera unit;providing a set of parameters for a second medication interventionevent, the set of second medication intervention parameters identifiablein camera unit data; comparing the accepted third data with the providedset of attributes for the individual and with the provided set ofparameters for the second medication intervention event; determining,from the comparison, if the accepted third data includes attributes ofthe individual and meets the parameters for the second medicationintervention event; and activating at least one indicator in response tothe third determination. An indicator can be attached, for example, tothe main computing unit (e.g. item 125 in FIG. 1), such asn indicatorlight or a computer display.

FIG. 97 illustrates aspects of a computer system 120 including at leastone main computing unit 125. Although a single main computing unit 125is illustrated in FIG. 97, in some embodiments there may be a pluralityof main computing units 125. A main computing unit 125 includescomputer-readable storage medium including executable instructions formonitoring medication events 9700. The computer-readable storage mediumincluding executable instructions for monitoring medication eventsrelating to an individual 9700 includes instructions 9710, 9720, 9730,9740. Instructions 9710 include instructions for presenting a set ofparameters for determining a first medication event for an individual,the set of parameters including at least one visual parameter and atleast one non-visual parameter. Instructions 9720 include instructionsfor comparing received data with the set of parameters for determiningthe first medication event for the individual. Instructions 9730 includeinstructions for determining a compliance likelihood for the firstmedication event based on the comparison. Instructions 9740 includeinstructions for indicating the determined compliance likelihood for thefirst medication event on a computing device.

As shown in FIG. 97, instructions 9710 include instructions forpresenting a set of parameters for determining a first medication eventfor an individual, the set of parameters including at least one visualparameter and at least one non-visual parameter. In some embodiments,instructions 9710 can include one or more additional instructions. Forexample, instructions 9710 can include instructions wherein theparameters include: at least one visual parameter specific to theindividual; at least one visual parameter specific to a medication; atleast one non-visual parameter specific to the individual; and at leastone non-visual parameter specific to the medication.

In some embodiments, the computer-readable storage medium includingexecutable instructions for monitoring medication events relating to anindividual 9700 includes additional instructions as well as instructions9710, 9720, 9730, 9740. For example, in some embodiments theinstructions include instructions for saving the determined compliancelikelihood into a memory. For example, in some embodiments theinstructions include instructions for saving the determined compliancelikelihood into a medical record for the individual. For example, insome embodiments the instructions include instructions for initiating atransmission including the determined compliance likelihood. Forexample, in some embodiments the instructions include instructions forsaving the received data into a memory.

FIG. 98 depicts a flowchart of a method 9800 for monitoring medicationevents. These method steps can be carried out, for example, by acomputer system (e.g. item 120 in FIG. 1). FIG. 98 shows that the methodincludes a series of steps, 9810, 9820, 9830, 9840. Method step 9810includes presenting a set of parameters for determining a firstmedication event for an individual, the set of parameters including atleast one visual parameter and at least one non-visual parameter. Methodstep 9820 includes comparing received data with the set of parametersfor determining the first medication event for the individual. Methodstep 9830 includes determining a compliance likelihood for the firstmedication event based on the comparison. Method step 9840 includesindicating the determined compliance likelihood for the first medicationevent on a computing device.

In some embodiments, the method 9800 can include additional steps. Forexample, in some embodiments the set of parameters including at leastone visual parameter and at least one non-visual parameter of methodstep 9810 includes: at least one visual parameter specific to theindividual; at least one visual parameter specific to a medication; atleast one non-visual parameter specific to the individual; and at leastone non-visual parameter specific to the medication.

In some embodiments, the method 9800 can include further steps as wellas the method steps 9810, 9820, 9830, 9840 illustrated in FIG. 98. Forexample, the method 9800 can include saving the determined compliancelikelihood into a memory. For example, the method 9800 can includesaving the determined compliance likelihood into a medical record forthe individual. For example, the method 9800 can include initiating atransmission including the determined compliance likelihood. Forexample, the method 9800 can include saving the received data into amemory.

FIG. 99 illustrates further aspects of the systems and methods describedherein. FIG. 99 illustrates aspects of a system for monitoringmedication events relating to an individual. The system can be acomputer system such as depicted in FIG. 1 and described herein. Thesystem 9900 depicted in FIG. 99 includes electrical circuitry. Thecircuitry of the system 9900 is configured to carry out a series oflogical processes. As illustrated in FIG. 99, a system 9900 formonitoring medication events relating to an individual includes one ormore circuitry components 9910, 9920, 9930, 9940. The circuitry isconfigured to carry out specific processes.

The system 9900 includes circuitry 9910 for presenting a set ofparameters for determining a first medication event for an individual,the set of parameters including at least one visual parameter and atleast one non-visual parameter. The system 9900 includes circuitry 9920for comparing received data with the set of parameters for determiningthe first medication event for the individual. The system 9900 includescircuitry 9930 for determining a compliance likelihood for the firstmedication event based on the comparison. The system 9900 includescircuitry 9940 for indicating the determined compliance likelihood forthe first medication event on a computing device.

FIG. 99 also shows that, in some embodiments, the system 9900 includesadditional aspects. For example, FIG. 99 shows that, in someembodiments, circuitry 9910 for presenting a set of parameters fordetermining a first medication event for an individual, the set ofparameters including at least one visual parameter and at least onenon-visual parameter includes circuitry 9950. Circuitry 9950 includes:circuitry including at least one visual parameter specific to theindividual; circuitry including at least one visual parameter specificto a medication; circuitry including at least one non-visual parameterspecific to the individual; and circuitry including at least onenon-visual parameter specific to the medication.

FIG. 99 further depicts that, in some embodiments the system 9900includes one or more additional aspects. For example, the system 9900can include one or more of circuitry 9960, 9970, 9980, 9990. Circuitry9960 includes circuitry for saving the determined compliance likelihoodinto a memory. Circuitry 9970 includes circuitry for saving thedetermined compliance likelihood into a medical record for theindividual. Circuitry 9980 includes circuitry for initiating atransmission including the determined compliance likelihood. Circuitry9990 includes circuitry for saving the received data into a memory.

FIG. 100 illustrates further aspects of the systems and methodsdescribed herein. FIG. 100 illustrates aspects of a system formonitoring medication events relating to an individual. The system canbe a computer system such as depicted in FIG. 1 and described herein.The system 10000 depicted in FIG. 100 includes electrical circuitry. Thecircuitry of the system 10000 is configured to carry out a series oflogical processes. As illustrated in FIG. 100, a system 10000 formonitoring medication events relating to an individual includes one ormore circuitry components 10010, 10020, 10030, 10040, 10050, 10060. Thecircuitry is configured to carry out specific processes.

The system 10000 includes circuitry 10010 for determining a start of amedication event interval for an individual. The system 10000 includescircuitry 10020 for receiving data from at least one camera unitassociated with the individual, the data including both visual data andnon-visual data. The system 10000 includes circuitry presenting a set ofparameters for determining a first medication event for an individual,the set of parameters including at least one visual parameter and atleast one non-visual parameter. The system 10000 includes circuitry10040 for comparing the received data with the set of parameters fordetermining the first medication event for the individual. The system10000 includes circuitry 10050 for determining a compliance likelihoodfor the first medication event based on the comparison. The system 10000includes circuitry 10060 for indicating the determined compliancelikelihood for the first medication event.

FIG. 101 illustrates aspects of a computer system 120 including at leastone main computing unit 125. Although a single main computing unit 125is illustrated in FIG. 101, in some embodiments there may be a pluralityof main computing units 125. A main computing unit 125 includescomputer-readable storage medium including executable instructions formonitoring medication events 10100. The computer-readable storage mediumincluding executable instructions for monitoring medication eventsrelating to an individual 10100 includes instructions 10110, 10120,10130, 10140. Instructions 10110 include instructions for determining astart of a medication event interval for an individual. Instructions10120 include instructions for receiving data from at least one cameraunit associated with the individual, the data including both visual dataand non-visual data. Instructions 10130 include instructions forpresenting a set of parameters for determining a first medication eventfor an individual, the set of parameters including at least one visualparameter and at least one non-visual parameter. Instructions 10140include instructions for comparing the received data with the set ofparameters for determining the first medication event for theindividual. Instructions 10150 include instructions for determining acompliance likelihood for the first medication event based on thecomparison. Instructions 10160 include instructions for indicating thedetermined compliance likelihood for the first medication event.

FIG. 102 illustrates a flowchart of a method 10200 for monitoringmedication events relating to an individual. These method steps can becarried out, for example, by a computer system (e.g. item 120 in FIG.1). FIG. 102 shows that the method includes a series of steps, 10210,10220, 10230, 10240, 10250, 10260. Method step 10210 includesdetermining a start of a medication event interval for an individual.Method step 10220 includes receiving data from at least one camera unitassociated with the individual, the data including both visual data andnon-visual data. Method step 10230 includes presenting a set ofparameters for determining a first medication event for an individual,the set of parameters including at least one visual parameter and atleast one non-visual parameter. Method step 10240 includes comparing thereceived data with the set of parameters for determining the firstmedication event for the individual. Method step 10250 includesdetermining a compliance likelihood for the first medication event basedon the comparison. Method step 10260 includes indicating the determinedcompliance likelihood for the first medication event. In someembodiments, additional method steps are included in the method.

A series of flowcharts depicting implementations are presented above.For ease of understanding, the flowcharts are organized such that theinitial flowcharts present implementations via an example implementationand thereafter the following flowcharts present alternateimplementations and/or expansions of the initial flowchart(s) as eithersub-component operations or additional component operations building onone or more earlier-presented flowcharts. The style of presentationutilized herein (e.g., beginning with a presentation of a flowchart(s)presenting an example implementation and thereafter providing additionsto and/or further details in subsequent flowcharts) generally allows fora rapid and easy understanding of the various process implementations.In addition, the style of presentation used herein also lends itselfwell to modular and/or object-oriented program design paradigms.

The foregoing detailed description has set forth various embodiments ofthe devices and/or processes via the use of block diagrams, flowcharts,and/or examples. Insofar as such block diagrams, flowcharts, and/orexamples contain one or more functions and/or operations, each functionand/or operation within such block diagrams, flowcharts, or examples canbe implemented, individually and/or collectively, by a wide range ofhardware, software, firmware, or a combination thereof. In oneembodiment, several portions of the subject matter described herein maybe implemented via Application Specific Integrated Circuits (ASICs),Field Programmable Gate Arrays (FPGAs), digital signal processors(DSPs), or other integrated formats. However, some aspects of theembodiments disclosed herein, in whole or in part, can be equivalentlyimplemented in integrated circuits, as one or more computer programsrunning on one or more computers (e.g., as one or more programs runningon one or more computer systems), as one or more programs running on oneor more processors (e.g., as one or more programs running on one or moremicroprocessors), as firmware, or as a combination thereof, and thatdesigning the circuitry and/or writing the code for the software and orfirmware would be well within the skill of one of skill in the art inlight of this disclosure. In addition, the mechanisms of the subjectmatter described herein are capable of being distributed as a programproduct in a variety of forms, and that an illustrative embodiment ofthe subject matter described herein applies regardless of the particulartype of signal bearing medium used to actually carry out thedistribution. Examples of a signal bearing medium include, but are notlimited to, the following: a recordable type medium such as a floppydisk, a hard disk drive, a Compact Disc (CD), a Digital Video Disk(DVD), a digital tape, a computer memory, etc.; and a transmission typemedium such as a digital and/or an analog communication medium (e.g., afiber optic cable, a waveguide, a wired communications link, a wirelesscommunication link (e.g., transmitter, receiver, transmission logic,reception logic, etc.), etc.).

In a general sense, the various embodiments described herein can beimplemented, individually and/or collectively, by various types ofelectro-mechanical systems having a wide range of electrical componentssuch as hardware, software, firmware, and/or virtually any combinationthereof; and a wide range of components that may impart mechanical forceor motion such as rigid bodies, spring or torsional bodies, hydraulics,electro-magnetically actuated devices, and/or virtually any combinationthereof. Consequently, as used herein “electro-mechanical system”includes, but is not limited to, electrical circuitry operably coupledwith a transducer (e.g., an actuator, a motor, a piezoelectric crystal,a Micro Electro Mechanical System (MEMS), etc.), electrical circuitryhaving at least one discrete electrical circuit, electrical circuitryhaving at least one integrated circuit, electrical circuitry having atleast one application specific integrated circuit, electrical circuitryforming a general purpose computing device configured by a computerprogram (e.g., a general purpose computer configured by a computerprogram which at least partially carries out processes and/or devicesdescribed herein, or a microprocessor configured by a computer programwhich at least partially carries out processes and/or devices describedherein), electrical circuitry forming a memory device (e.g., forms ofmemory (e.g., random access, flash, read only, etc.)), electricalcircuitry forming a communications device (e.g., a modem, communicationsswitch, optical-electrical equipment, etc.), and/or any non-electricalanalog thereto, such as optical or other analogs (e.g., graphene basedcircuitry). Examples of electro-mechanical systems include but are notlimited to a variety of consumer electronics systems, medical devices,as well as other systems such as motorized transport systems, factoryautomation systems, security systems, and/or communication/computingsystems. Electro-mechanical, as used herein, is not necessarily limitedto a system that has both electrical and mechanical actuation except ascontext may dictate otherwise.

In a general sense, the various aspects described herein can beimplemented, individually and/or collectively, by a wide range ofhardware, software, firmware, and/or any combination thereof can beviewed as being composed of various types of “electrical circuitry.”Consequently, as used herein “electrical circuitry” includes, but is notlimited to, electrical circuitry having at least one discrete electricalcircuit, electrical circuitry having at least one integrated circuit,electrical circuitry having at least one application specific integratedcircuit, electrical circuitry forming a general purpose computing deviceconfigured by a computer program (e.g., a general purpose computerconfigured by a computer program which at least partially carries outprocesses and/or devices described herein, or a microprocessorconfigured by a computer program which at least partially carries outprocesses and/or devices described herein), electrical circuitry forminga memory device (e.g., forms of memory (e.g., random access, flash, readonly, etc.)), and/or electrical circuitry forming a communicationsdevice (e.g., a modem, communications switch, optical-electricalequipment, etc.). The subject matter described herein may be implementedin an analog or digital fashion or some combination thereof.

At least a portion of the devices and/or processes described herein canbe integrated into an image processing system. A typical imageprocessing system generally includes one or more of a system unithousing, a video display device, memory such as volatile or non-volatilememory, processors such as microprocessors or digital signal processors,computational entities such as operating systems, drivers, applicationsprograms, one or more interaction devices (e.g., a touch pad, a touchscreen, an antenna, etc.), control systems including feedback loops andcontrol motors (e.g., feedback for sensing lens position and/orvelocity; control motors for moving/distorting lenses to give desiredfocuses). An image processing system may be implemented utilizingsuitable commercially available components, such as those typicallyfound in digital still systems and/or digital motion systems.

At least a portion of the devices and/or processes described herein canbe integrated into a data processing system. A data processing systemgenerally includes one or more of a system unit housing, a video displaydevice, memory such as volatile or non-volatile memory, processors suchas microprocessors or digital signal processors, computational entitiessuch as operating systems, drivers, graphical user interfaces, andapplications programs, one or more interaction devices (e.g., a touchpad, a touch screen, an antenna, etc.), and/or control systems includingfeedback loops and control motors (e.g., feedback for sensing positionand/or velocity; control motors for moving and/or adjusting componentsand/or quantities). A data processing system may be implementedutilizing suitable commercially available components, such as thosetypically found in data computing/communication and/or networkcomputing/communication systems.

With respect to the use of substantially any plural and/or singularterms herein, it is possible to translate from the plural to thesingular and/or from the singular to the plural as is appropriate to thecontext and/or application. The various singular/plural permutations arenot expressly set forth herein for sake of clarity.

The herein described subject matter sometimes illustrates differentcomponents contained within, or connected with, different othercomponents. It is to be understood that such depicted architectures aremerely exemplary, and that in fact many other architectures may beimplemented which achieve the same functionality. In a conceptual sense,any arrangement of components to achieve the same functionality iseffectively “associated” such that the desired functionality isachieved. Hence, any two components herein combined to achieve aparticular functionality can be seen as “associated with” each othersuch that the desired functionality is achieved, irrespective ofarchitectures or intermedial components. Likewise, any two components soassociated can also be viewed as being “operably connected”, or“operably coupled,” to each other to achieve the desired functionality,and any two components capable of being so associated can also be viewedas being “operably couplable,” to each other to achieve the desiredfunctionality. Specific examples of operably couplable include but arenot limited to physically mateable and/or physically interactingcomponents, and/or wirelessly interactable, and/or wirelesslyinteracting components, and/or logically interacting, and/or logicallyinteractable components. In some instances, one or more components maybe referred to herein as “configured to,” “configured by,” “configurableto,” “operable/operative to,” “adapted/adaptable,” “able to,”“conformable/conformed to,” etc. Such terms (e.g. “configured to”) cangenerally encompass active-state components and/or inactive-statecomponents and/or standby-state components, unless context requiresotherwise.

While particular aspects of the present subject matter described hereinhave been shown and described, it will be apparent that, based upon theteachings herein, changes and modifications may be made withoutdeparting from the subject matter described herein and its broaderaspects and, therefore, the appended claims are to encompass withintheir scope all such changes and modifications as are within the truespirit and scope of the subject matter described herein. In general,terms used herein, and especially in the appended claims (e.g., bodiesof the appended claims) are generally intended as “open” terms (e.g.,the term “including” should be interpreted as “including but not limitedto,” the term “having” should be interpreted as “having at least,” theterm “includes” should be interpreted as “includes but is not limitedto,” etc.). When a specific number of an introduced claim recitation isintended, such an intent will be explicitly recited in the claim, and inthe absence of such recitation no such intent is present. For example,as an aid to understanding, the following appended claims contain usageof the introductory phrases “at least one” and “one or more” tointroduce claim recitations. However, the use of such phrases should notbe construed to imply that the introduction of a claim recitation by theindefinite articles “a” or “an” limits any particular claim containingsuch introduced claim recitation to claims containing only one suchrecitation, even when the same claim includes the introductory phrases“one or more” or “at least one” and indefinite articles such as “a” or“an” (e.g., “a” and/or “an” should typically be interpreted to mean “atleast one” or “one or more”); the same holds true for the use ofdefinite articles used to introduce claim recitations. In addition, evenif a specific number of an introduced claim recitation is explicitlyrecited, such recitation should typically be interpreted to mean atleast the recited number (e.g., the bare recitation of “tworecitations,” without other modifiers, typically means at least tworecitations, or two or more recitations). Furthermore, in thoseinstances where a convention analogous to “at least one of A, B, and C,etc.” is used, in general such a construction is intended in the senseof the above (e.g., “a system having at least one of A, B, and C” wouldinclude but not be limited to systems that have A alone, B alone, Calone, A and B together, A and C together, B and C together, and/or A,B, and C together, etc.). In those instances where a constructionanalogous to “at least one of A, B, or C, etc.” is used, in general sucha construction is intended in the sense one having skill in the artwould understand the convention (e.g., “a system having at least one ofA, B, or C” would include but not be limited to systems that have Aalone, B alone, C alone, A and B together, A and C together, B and Ctogether, and/or A, B, and C together, etc.). It will be furtherunderstood that typically a disjunctive word and/or phrase presentingtwo or more alternative terms, whether in the description, claims, ordrawings, should be understood to contemplate the possibilities ofincluding one of the terms, either of the terms, or both terms unlesscontext dictates otherwise. For example, the phrase “A or B” will betypically understood to include the possibilities of “A” or “B” or “Aand B.”

With respect to the appended claims, recited operations therein maygenerally be performed in any order. Also, although various operationalflows are presented in a sequence(s), it should be understood that thevarious operations may be performed in other orders than those which areillustrated, or may be performed concurrently. Examples of suchalternate orderings may include overlapping, interleaved, interrupted,reordered, incremental, preparatory, supplemental, simultaneous,reverse, or other variant orderings, unless context dictates otherwise.Furthermore, terms like “responsive to,” “related to,” or otherpast-tense adjectives are generally not intended to exclude suchvariants, unless context dictates otherwise.

The foregoing specific exemplary processes and/or devices and/ortechnologies are representative of more general processes and/or devicesand/or technologies taught elsewhere herein, such as in the claims filedherewith and/or elsewhere in the present application.

All of the above U.S. patents, U.S. patent application publications,U.S. patent applications, foreign patents, foreign patent applicationsand non-patent publications referred to in this specification and/orlisted in any Application Data Sheet, are incorporated herein byreference, to the extent not inconsistent herewith.

While various aspects and embodiments have been disclosed herein, otheraspects and embodiments will be apparent. The various aspects andembodiments disclosed herein are for purposes of illustration and arenot intended to be limiting, with the true scope and spirit beingindicated by the following claims.

What is claimed is: 1.-551. (canceled)
 552. A method for monitoringmedication events, comprising: accepting first data from a camera unitassociated with an individual; providing a set of medicationintervention parameters for the individual; comparing the accepted firstdata from the camera unit associated with the individual with theprovided set of medication intervention parameters for the individual;determining if the accepted first data is within the provided set ofmedication intervention parameters; activating at least one indicator inresponse to the first determination; accepting second data from thecamera unit associated with the individual, the second data obtainedafter the activation of the at least one indicator; analyzing theaccepted second data for at least one attribute relating to themedication event; comparing the accepted second data with the providedset of medication intervention parameters for the individual;determining if the accepted second data is within the provided set ofmedication intervention parameters; and activating the at least oneindicator in response to the second determination.
 553. The method ofclaim 552, wherein the accepting first data from a camera unitassociated with an individual comprises: accepting visual data andaccepting non-visual data. 554.-561. (canceled)
 562. The method of claim552, wherein the accepting first data from a camera unit associated withan individual comprises: accepting data including audio data. 563.-564.(canceled)
 565. The method of claim 552, wherein the providing a set ofmedication intervention parameters for the individual comprises:providing a set of medication intervention parameters for the individualincluding audio parameters. 566.-568. (canceled)
 569. The method ofclaim 552, wherein the comparing the accepted first data from the cameraunit associated with the individual with the provided set of medicationintervention parameters for the individual comprises: comparing theaccepted first data with at least one minimum sufficiency parameter.570.-577. (canceled)
 578. The method of claim 552, wherein the acceptingsecond data from the camera unit associated with the individual, thesecond data obtained after the activation of the at least one indicator,comprises: accepting data including visual data, non-visual data, and atleast one time value. 579.-580. (canceled)
 581. The method of claim 552,wherein the analyzing the accepted second data for at least oneattribute relating to a medication event comprises: analyzing theaccepted second data for at least one non-visual attribute. 582.-593.(canceled)
 594. The method of claim 552, comprising: accepting thirddata from the camera unit associated with the individual, the third dataobtained after the activation of the at least one indicator in responseto the second determination; analyzing the accepted third data for theat least one attribute relating to the medication event; comparing theaccepted third data with the provided set of medication interventionparameters for the individual; determining if the accepted third data iswithin the provided set of medication intervention parameters; andactivating the at least one indicator in response to the thirddetermination. 595.-706. (canceled)
 707. A method for monitoringmedication events, comprising: providing a set of attributes for anindividual, the set of attributes identifiable in camera unit data;providing a set of medication condition parameters for the individual,the set of medication condition parameters identifiable in camera unitdata; accepting first data from at least one camera unit; comparing theaccepted first data with the provided set of attributes for theindividual and with the provided set of medication condition parametersfor the individual; determining, from the comparison, if the acceptedfirst data includes attributes of the individual and meets themedication condition parameters; initiating a first medicationintervention event, dependent on the determination from the comparison;accepting second data from the at least one camera unit; providing a setof parameters for the first medication intervention event, the set offirst medication intervention parameters identifiable in camera unitdata; comparing the accepted second data with the provided set ofattributes for the individual and with the provided set of parametersfor the first medication intervention event; determining, from thecomparison, if the accepted second data includes attributes of theindividual and meets the parameters for the first medicationintervention event; and activating at least one indicator in response tothe second determination.
 708. The method of claim 707, wherein theproviding a set of attributes for an individual, the set of attributesidentifiable in camera unit data, comprises: providing visualattributes; and providing non-visual attributes. 709.-711. (canceled)712. The method of claim 707, wherein the providing a set of attributesfor an individual, the set of attributes identifiable in camera unitdata, comprises: providing a set of attributes identifiable in cameraunit data including video data. 713.-714. (canceled)
 715. The method ofclaim 707, wherein the providing a set of attributes for an individual,the set of attributes identifiable in camera unit data, comprises:providing a set of attributes identifiable in camera unit data includingaudio data. 716.-722. (canceled)
 723. The method of claim 707, whereinthe providing a set of medication condition parameters for theindividual, the set of medication condition parameters identifiable incamera unit data, comprises: providing a set of parameters includingaudio parameters. 724.-730. (canceled)
 731. The method of claim 707,wherein the accepting first data from at least one camera unitcomprises: accepting audio data. 732.-739. (canceled)
 740. The method ofclaim 707, wherein the comparing the accepted first data with theprovided set of attributes for the individual and with the provided setof medication condition parameters for the individual comprises:comparing visual and non-visual components of the accepted first datawith the provided set of medication condition parameters for theindividual and with the provided set of medication condition parametersfor the individual.
 741. The method of claim 707, wherein thedetermining, from the comparison, if the accepted first data includesattributes of the individual and meets the medication conditionparameters, comprises: determining, from the comparison, if the acceptedfirst data meets both visual an non-visual aspects of the medicationcondition parameters. 742.-757. (canceled)
 758. The method of claim 707,comprising: processing the at least one accepted first data; processingthe at least one accepted second data; integrating the processed atleast one accepted first data and the processed at least one acceptedsecond data into a medication record; and saving the medication recordin a memory.
 759. (canceled)
 760. The method of claim 707, comprising:indicating, to at least one system user, the initiating a firstmedication intervention event. 761.-762. (canceled)
 763. Acomputer-readable storage medium including executable instructions formonitoring medication events relating to an individual, thecomputer-readable storage medium comprising: instructions for presentinga set of parameters for determining a first medication event for anindividual, the set of parameters including at least one visualparameter and at least one non-visual parameter; instructions forcomparing received data with the set of parameters for determining thefirst medication event for the individual; instructions for determininga compliance likelihood for the first medication event based on thecomparison; and instructions for indicating the determined compliancelikelihood for the first medication event on a computing device.764.-768. (canceled)
 769. A method for monitoring medication eventsrelating to an individual, comprising: presenting a set of parametersfor determining a first medication event for an individual, the set ofparameters including at least one visual parameter and at least onenon-visual parameter; comparing received data with the set of parametersfor determining the first medication event for the individual;determining a compliance likelihood for the first medication event basedon the comparison; and indicating the determined compliance likelihoodfor the first medication event on a computing device. 770.-774.(canceled)
 775. A system for monitoring medication events relating to anindividual, comprising: circuitry for presenting a set of parameters fordetermining a first medication event for an individual, the set ofparameters including at least one visual parameter and at least onenon-visual parameter; circuitry for comparing received data with the setof parameters for determining the first medication event for theindividual; circuitry for determining a compliance likelihood for thefirst medication event based on the comparison; and circuitry forindicating the determined compliance likelihood for the first medicationevent on a computing device. 776.-783. (canceled)